#perl
01 January 2008
Total 32 pages. You are browsing page 32/32.
First :: Prev :: [...] [28] [29] [30] [31] [32] :: Next :: Last
22:41 <****> it's odd cuz I'm not using the e-mail address field at all in my template
22:41 <****> or in my prog
22:41 <****> it seems just performing a query and building the data object causes the problem
22:41 <****> perlmonkey: DBIC doesn't use eval during that process
22:42 <****> not string eval, which is what that error is
22:42 <****> im really puzzled then
22:46 * CPAN upload: NetHack-Menu-0.02 by SARTAK
22:47 <****> perlmonkey: Devel::SimpleTrace
22:47 <****> ok
22:50 <****> \tat Carp::croak(unknown source), :-|
22:51 <****> /6/6
22:51 <****> damnit.
22:52 * perlmonkey has headache
22:54 <****> something freaky going on which I can't control
22:56 <****> Can someone point me on a way to close nicely a script when a SIG TERM happens ? I would like to make it a task before exiting
22:56 <****> you know about %SIG?
22:57 <****> does anyone have the number for ghostbusters
22:58 <****> anno-: I google a lot with SIG and I haven't find something clear
22:59 <****> perldoc perlvar
22:59 <****> perlmonkey: 0118 999 881 999 119 725 3
22:59 <****> :P
22:59 <****> google isn't for everything
23:01 <****> yes you are right this is ok : http://www.ccsf.edu/Pub/Perl/perlipc/Signals.html
23:02 <****> tits, alester went
23:09 * perlmonkey feels like a total c*nt
23:09 <****> solved the problem
23:10 <****> the column was in the wrong place, the email addresses were going to the wrong place
23:10 * perlmonkey been on the guinness
23:11 <****> dubphil: something like $SIG{TERM}=sub{die $!} should give you the hint.
23:12 <****> maldous: ok thanks !
23:13 <****> maldous: why $!? there's no system error involved
23:13 <****> dubphil: is this in your POE program?
23:13 <****> yes pravus
23:14 <****> dubphil: then you'd want to use POE's signal handling
23:14 <****>sig() in POE::Kernel
23:31 * CPAN upload: Process-0.21 by ADAMK
23:31 * CPAN upload: XML-Elemental-2.011 by TIMA
23:39 <****> how would I structure a regex to parse [option1[,option2[,option3]]]?
23:40 <****> ok for how to do it , now the problem is how to know the good signal to use, it doesn't work when I use INT or TERM
23:40 <****> findlay: are you sure a regex is the best option?
23:40 <****> thrig: no
23:40 <****> just parsing command line arguments
23:40 <****> guess I could structure it differently
23:41 <****> there are Getopt::* modules available...
23:43 <****> the thing with Getopt though is I will still have to parse the arguments with a sub
23:43 <****> how so?
23:44 <****> well I don't want to have to say --arg1=1 --arg2=2, etc.
23:44 <****> what are you trying to parse?
23:45 <****> this script is going to read arguments (purchase order # and product type(s)) and go find the corresponding files and print them
23:46 * CPAN upload: XML-Atom-Syndication-0.942 (++ ) by TIMA
23:46 <****> --po-numbers=1234,2345,... and then @po_nums = split ',', $some_arg
23:46 <****> use Getopt::Long to convert --po-numbers into $some_arg
23:47 <****> but the the problem is that each PO has up to 3 product types, and usually not all types need to be printed out
23:48 <****> so I need to specify which types of which PO should be printed
23:48 <****> how is that a problem?
23:49 <****> how would you do it?
23:49 <****> I would hire thrig to write it for me ;)
23:49 <****> heh
23:49 <****> what, specify a list of product types? Didn't I just show a Very Similar example?
23:49 <****> I don't see how your example applies
23:50 <****> well, maybe
23:50 <****> findlay: his example does exactly what you want.
23:50 <****> findlay: read up on Getop::Long
23:51 <****> @not_po_numbers_but_instead_types_to_print = split ',', $some_other_arg (and etc.)
23:51 <****> how to know the good signal to use, it doesn't work when I use INT or TERM when we use $SIG[something] ?
23:51 <****> of course $SIG[something] doesn't work. Why would it?
23:52 <****> $SIG{} what can I put inside the brackets ?
23:53 <****> thrig: I need to print 123/type1 and 124/type2,type3 and 125/type2. I don't see your example does this
23:53 <****> that comes later. You need to code it, or hire someone.
23:53 <****> dubphil: perldoc perlipc
23:53 <****> k, well just making sure I understood what you were saying
--- Log closed Wed Jan 02 00:00:06 2008
Total 32 pages. You are browsing page 32/32.
First :: Prev :: [...] [28] [29] [30] [31] [32] :: Next :: Last