|
|
|
| more useful options | |
| PerlMonks |
Re: Binding C librariesby adamk (Chaplain) |
| on Feb 08, 2005 at 02:33 UTC ( [id://428955]=note: print w/replies, xml ) | Need Help?? |
This is an archived low-energy page for bots and other anonmyous visitors. Please sign up if you are a human and want to interact.
The prevailing attitude seems to be OO with added procedural options if you can provide the functionality in a simple one-shot function. Regardless, do not export by default. I mean it! PLEASE PLEASE PLEASE We've been telling people not to do this for while, but standards seem to be slipping a little lately, with even quite new modules exporting things like "copy" into the callers namespace. My suspicion is that it is because many of the older File:: module do this, and so people think that it is ok. Your one exception might be if the most likely name is something truly odd, like "encode_rfc30042" that is pretty much NEVER going to collide with anything.
In Section
Seekers of Perl Wisdom
|
|
||||||||||||||||||||||||