Re: Specifying the class of an object in the declaration

You can find out the gory details on CPAN at TheSchwartz::Job and TheSchwartz. In general, if you see something that looks like a package name and you aren't sure what it does , CPAN is a good place to start searching.

As for the merits of this particular job queue/management package, I'll pass and let some of our job and threading experts handle that.

Comment on Re: Specifying the class of an object in the declaration

Replies are listed 'Best First'.
Re^2: Specifying the class of an object in the declaration by FalseVinylShrub (Chaplain) on Jan 13, 2011 at 12:54 UTC
Hi Thanks for the rapid reply. It's not so much TheSchwartz that I'm confused about, though I've never used it before, but rather that particular construct: `my CLASSNAME $variable = something`. I've never seen it before, and nor have my cow-orkers. It's not particularly stopping me from doing anything, I just don't like not understanding something ;-) FalseVinylShrub Disclaimer: Please review and test code, and use at your own risk... If I answer a question, I would like to hear if and how you solved your problem.	[reply] [d/l]
Re^3: Specifying the class of an object in the declaration by ELISHEVA (Prior) on Jan 13, 2011 at 13:11 UTC
Ah. Well, according to the documentation of my: my TYPE expression The exact semantics and interface of TYPE and ATTRS are still evolving. TYPE is currently bound to the use of fields pragma, and attributes are handled using the attributes pragma, or starting from Perl 5.8.0 also via the Attribute::Handlers module. See Private Variables via my() in perlsub for details, and fields, attributes, and Attribute::Handlers.	[reply]
Re^4: Specifying the class of an object in the declaration by FalseVinylShrub (Chaplain) on Jan 14, 2011 at 09:37 UTC
Hi Thanks, that was what I was missing ;-) FalseVinylShrub Disclaimer: Please review and test code, and use at your own risk... If I answer a question, I would like to hear if and how you solved your problem.	[reply]