The "Geo" top-level namespace is appropriate. How about Geo-WinDesc?
That seems to fit if the data format is known primarily after its
originating application.
cpan[1]> d //Geo-/
Reading '/home/daxim/.local/share/.cpan/Metadata'
Database was generated on Mon, 05 Aug 2013 19:53:02 GMT
On Mon, 05 Aug 2013 11:45:52 -0500
Brian Katzung wrote:
> Good point. I read the OP's example and understood it to be
> case-insensitive, but even having seen it spelled out still didn't
> protect me from forgetting the detail (a "broken understanding")
> later. :-)
Having it spelled out is su
On 2013-08-05 10:58, David Cantrell wrote:
On Sun, Aug 04, 2013 at 03:28:23PM -0400, Shawn H Corey wrote:
On Sun, 04 Aug 2013 14:13:59 -0500
Brian Katzung wrote:
That's an interesting idea, but I'm not sure you're accomplishing
your stated goals. Consider that the RE /^\s*test\s*$/ is 14
chara
Hello,
I'm seeking help naming my Perl module to parse the save file format
of a specific application. The module will likely stay read-only as I
don't assume demand exists for writing. I've looked at both
File::Format:: and Parse:: but the former seems abandoned and the
latter doesn't seem a go
On Sun, Aug 04, 2013 at 03:28:23PM -0400, Shawn H Corey wrote:
> On Sun, 04 Aug 2013 14:13:59 -0500
> Brian Katzung wrote:
> > That's an interesting idea, but I'm not sure you're accomplishing
> > your stated goals. Consider that the RE /^\s*test\s*$/ is 14
> > characters and you've coded it in 91
On Sun, Aug 04, 2013 at 01:30:55PM -0400, Shawn H Corey wrote:
> On Sun, 4 Aug 2013 18:03:51 +0200
> Lars D? ? wrote:
> > This would be better in the Regexp top level namespace instead of
> > occupying its own:
> I chose the short name so it would be remembered. Long names
