Re: Is it a pragma or a module?

It's kind of like deciding what is a medicine and what is simply an herbal remedy. A pragma, in concept, means that it changes the actual core Perl language in some way so that it is better able to work with you on expressing a solution. A non-pragma module, in concept, offers you a set of tools separate from the actual Perl language, with which you build your solution. Clear enough for you? Sometimes, me neither.

--
[ e d @ h a l l e y . c c ]

Comment on Re: Is it a pragma or a module?

Replies are listed 'Best First'.
Re^2: Is it a pragma or a module? by strat (Canon) on Dec 15, 2006 at 09:47 UTC
halley: I like your explanation, although I'd add that it needs to be delivered with core perl. Otherwize, all modules using source filters would become additional pragmata. Best regards, perl -e "s>>F>e=>y)\martinF)stronat)=>print,print v8.8.8.32.11.32"	[reply]
Re^3: Is it a pragma or a module? by halley (Prior) on Dec 18, 2006 at 00:40 UTC
I don't agree that being in the core perl distribution is a trait of pragmatic modules. See my use deprecated; node. -- `[ e d @ h a l l e y . c c ]`	[reply]