zframe_reset_zero_copy removed due to multiple errors
- if free_fn is null, ignores data
- at end, copies data in any case, so isn't zero-copy
- makes API complex for uncertain benefit
Zero-copy methods slated for removal

There are multiple problems with these methods but mainly the accumulation
of technical debt for uncertain benefit. It makes the CZMQ API complex and
is arguably a case of premature optimization. Real zero-copy use cases are
very rare and they can work directly with the zmq_msg API. The zero-copy
semantics have also leaked in confusing ways (e.g. zframe_freefn). Some of
the methods copied data in any case.

If we really want a zero copy API in CZMQ we should put this into a
single znocopy module with clear semantics, and we should design a nicer
zero-copy API.
Ignoring ENOTSOCK error from zsock_set_linger
Adding a more informational assert
Merge pull request #176 from jlopezr/master

Generates a more informative assert when the user calls zsocket_destroy with a void** instead of a void*
Merge pull request #177 from hintjens/master

Marking zero-copy methods as deprecated