Skip Menu |

This queue is for tickets about the Getopt-Param-Tiny CPAN distribution.

Report information
The Basics
Id: 34586
Status: open
Priority: 0/
Queue: Getopt-Param-Tiny

People
Owner: Nobody in particular
Requestors: adamk [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: (no value)
Fixed in: (no value)



Subject: Makefile.PL is not primitive enough
The Makefile.PL makes use of use warnings. This will blow up on anything older than 5.006 (Tiny modules try to attain 5.004 support). It's probably also a good idea to remove Build.PL as well for this and just go with raw high-legacy-compatible Makefile.PL
Subject: Re: [rt.cpan.org #34586] AutoReply: Makefile.PL is not primitive enough
Date: Tue, 01 Apr 2008 16:28:18 +1100
To: bug-Getopt-Param-Tiny [...] rt.cpan.org
From: Adam Kennedy <adamkennedybackup [...] gmail.com>
As an aside, I'd recommend you keep "use strict" in the code. It keeps the code clean and is going to be used anyway by almost every program in existance (either direct or via a module) So strict.pm is basically free. Adam K Bugs in Getopt-Param-Tiny via RT wrote: Show quoted text
> Greetings, > > This message has been automatically generated in response to the > creation of a trouble ticket regarding: > "Makefile.PL is not primitive enough", > a summary of which appears below. > > There is no need to reply to this message right now. Your ticket has been > assigned an ID of [rt.cpan.org #34586]. Your ticket is accessible > on the web at: > > http://rt.cpan.org/Ticket/Display.html?id=34586 > > Please include the string: > > [rt.cpan.org #34586] > > in the subject line of all future correspondence about this issue. To do so, > you may reply to this message. > > Thank you, > bug-Getopt-Param-Tiny@rt.cpan.org > > ------------------------------------------------------------------------- > The Makefile.PL makes use of use warnings. > > This will blow up on anything older than 5.006 (Tiny modules try to > attain 5.004 support). > > It's probably also a good idea to remove Build.PL as well for this and > just go with raw high-legacy-compatible Makefile.PL >
From: dmuey [...] cpan.org
On Tue Apr 01 01:32:48 2008, ADAMK wrote: Show quoted text
> The Makefile.PL makes use of use warnings. > > This will blow up on anything older than 5.006 (Tiny modules try to > attain 5.004 support). > > It's probably also a good idea to remove Build.PL as well for this and > just go with raw high-legacy-compatible Makefile.PL
Whoops, just did 0.2 before I saw this report, will be in 0.3 in the next few minutes, thanks!
On Tue Apr 01 01:34:51 2008, adamkennedybackup@gmail.com wrote: Show quoted text
> As an aside, I'd recommend you keep "use strict" in the code. > > It keeps the code clean and is going to be used anyway by almost every > program in existance (either direct or via a module) > > So strict.pm is basically free.
Generally I would agree, the constraints of an uber memory efficient project I am working on have strict disabled in production so I decided to leave it out in production here to since it won't gain us anything in this case. (then if they want to use it elsewhere they can no problem) I will add note to that effect in the code to avoid ambiguity but I'd like to shave off as much memory as possible and strict add 184K (plus you know have to 'use vars' which bumps it up to 272K) multivac:lib-tiny dmuey$ perl -e 'print `ps u -p $$`;' USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND dmuey 9207 0.7 0.1 601232 1168 s000 S+ 8:58AM 0:00.01 perl -e print `ps u -p $$`; multivac:lib-tiny dmuey$ perl -e 'use strict;print `ps u -p $$`;' USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND dmuey 9209 0.0 0.1 601232 1352 s000 S+ 8:58AM 0:00.01 perl -e use strict;print `ps u -p $$`; multivac:lib-tiny dmuey$
On Tue Apr 01 01:32:48 2008, ADAMK wrote: Show quoted text
> The Makefile.PL makes use of use warnings. > > This will blow up on anything older than 5.006 (Tiny modules try to > attain 5.004 support). > > It's probably also a good idea to remove Build.PL as well for this and > just go with raw high-legacy-compatible Makefile.PL
Applying to Getopt::Param::Tiny and lib::tiny
On Tue Apr 01 01:32:48 2008, ADAMK wrote: Show quoted text
> The Makefile.PL makes use of use warnings. > > This will blow up on anything older than 5.006 (Tiny modules try to > attain 5.004 support). > > It's probably also a good idea to remove Build.PL as well for this and > just go with raw high-legacy-compatible Makefile.PL
Applying to next Getopt::Param::Tiny and lib::tiny 0.3
On Tue Apr 01 01:32:48 2008, ADAMK wrote: Show quoted text
> The Makefile.PL makes use of use warnings. > > This will blow up on anything older than 5.006 (Tiny modules try to > attain 5.004 support). > > It's probably also a good idea to remove Build.PL as well for this and > just go with raw high-legacy-compatible Makefile.PL
Applying to next Getopt::Param::Tiny and lib::tiny 0.3
Subject: Re: [rt.cpan.org #34586] Makefile.PL is not primitive enough
Date: Wed, 02 Apr 2008 01:06:08 +1100
To: bug-Getopt-Param-Tiny [...] rt.cpan.org
From: Adam Kennedy <adamkennedybackup [...] gmail.com>
Daniel Muey via RT wrote: Show quoted text
> <URL: http://rt.cpan.org/Ticket/Display.html?id=34586 > > > On Tue Apr 01 01:34:51 2008, adamkennedybackup@gmail.com wrote: >
>> As an aside, I'd recommend you keep "use strict" in the code. >> >> It keeps the code clean and is going to be used anyway by almost every >> program in existance (either direct or via a module) >> >> So strict.pm is basically free. >>
> > Generally I would agree, the constraints of an uber memory efficient project I am working on > have strict disabled in production so I decided to leave it out in production here to since it > won't gain us anything in this case. (then if they want to use it elsewhere they can no > problem) > > I will add note to that effect in the code to avoid ambiguity but I'd like to shave off as much > memory as possible and strict add 184K (plus you know have to 'use vars' which bumps it up > to 272K) >
I've been avoiding use vars myself, yes. The idea of using Perl in a situation you can't afford the cost of use strict is interesting though, if you need it at some point I'd consider removing it from the other ::tiny modules. Personally, in such a constrained environment, I would have imagined something like Python (with it's very very small runtime) or more likely compiled langauges would be more appropriate. Adam K
Applied these points, and a few other things, to lib::tiny 0.4, Unix::PID::Tiny 0.3, Getopt::Param::Tiny 0.4 thanks for your time Adam, I reallya ppreciate it Show quoted text
> I've been avoiding use vars myself, yes.
Any suggestions as alternatives to our() and use vars() that works under strict without restricting to inside use (IE my()) would be more than welcome.
Subject: Re: [rt.cpan.org #34586] Makefile.PL is not primitive enough
Date: Wed, 02 Apr 2008 10:02:19 +1100
To: bug-Getopt-Param-Tiny [...] rt.cpan.org
From: Adam Kennedy <adamkennedybackup [...] gmail.com>
Daniel Muey via RT wrote: Show quoted text
> <URL: http://rt.cpan.org/Ticket/Display.html?id=34586 > > > Applied these points, and a few other things, to lib::tiny 0.4, Unix::PID::Tiny 0.3, > Getopt::Param::Tiny 0.4 > > thanks for your time Adam, I reallya ppreciate it > >
>> I've been avoiding use vars myself, yes. >>
> > Any suggestions as alternatives to our() and use vars() that works under strict without > restricting to inside use (IE my()) would be more than welcome. >
Just fully reference all variables of that type. $Module::Name::VERSION = '0.01'; etc etc...
Subject: Re: [rt.cpan.org #34586] Makefile.PL is not primitive enough
Date: Wed, 2 Apr 2008 08:40:40 -0500
To: bug-Getopt-Param-Tiny [...] rt.cpan.org
From: Dan Muey <webmaster [...] simplemood.com>
On Apr 1, 2008, at 6:08 PM, Adam Kennedy via RT wrote: Show quoted text
> > Queue: Getopt-Param-Tiny > Ticket <URL: http://rt.cpan.org/Ticket/Display.html?id=34586 > > > Daniel Muey via RT wrote:
>> <URL: http://rt.cpan.org/Ticket/Display.html?id=34586 > >> >> Applied these points, and a few other things, to lib::tiny 0.4, >> Unix::PID::Tiny 0.3, >> Getopt::Param::Tiny 0.4 >> >> thanks for your time Adam, I reallya ppreciate it >> >>
>>> I've been avoiding use vars myself, yes. >>>
>> >> Any suggestions as alternatives to our() and use vars() that works >> under strict without >> restricting to inside use (IE my()) would be more than welcome. >>
> Just fully reference all variables of that type. > > $Module::Name::VERSION = '0.01'; > > etc etc...
holy smokes, I am an idiot.. thanks!