Re: Module submission Devel::Constants

2001-10-11 Thread chromatic
On Thursday 11 October 2001 14:32, Tim Bunce wrote: > BTW, the Devel:: namespace isn't right for this. Devel:: is for > development-time tools, not run-time. That makes sense. What would you suggest? My first thought was constant::flags, but that's the pragma namespace. Something like Consta

Re: Module submission Devel::Constants

2001-10-10 Thread chromatic
On Wednesday 10 October 2001 20:43, Matthew Sachs wrote: > chromatic writes that he wants to have something similar to 'use > constant', but which also lets you get the name of the constant - not > just its value. He goes on to discuss the implementation: > I usually u

Re: Module submission Devel::Constants

2001-10-09 Thread chromatic
the module's published interface, attempting to read the flags returns a number like '24' instead of 'RST ACK SYN' or whatever. My solution is to overload constant::import, stashing away the names and values, so they can be fetched at runtime. Does that help? -- chromatic

PAUSE id request

2000-11-29 Thread chromatic
Here's the vitals: chromatic [EMAIL PROTECTED] http://wgz.org/chromatic/ CHROMATIC I've written a Crypt::CipherSaber module that I would like to contribute as soon as possible, and am developing other modules. The module description is as follows: Crypt::CipherSaber bdpo OO modul