On Dec 12, 2003, at 10:42 AM, drieux wrote: [..]
[..]Yes, and No. Again the presumption here is that we are discussing at the 'professional obligations level' and not at the academic/hobby level.
<flame> Drieux! You KankerousBoilOnTheBottomSideOfYourSithLord! That whole academic v. professional issue is CLOSED!!! </flame>
someone needed to get seriously flamed in this thread, and well, we just need to improve the quality of flaming to begin with.
Then there is the minor mechanical point that has been missed in the discussion so far
perldoc -m Foo::Bar
will allow one to see the 'internals' of the Foo::Bar module itself and not merely the POD.
Unlike the 'standard c libraries' - which tend to be raw binaries, unless one happens to have the source tree for them, perl is very open about the process. Which is both good and bad.
The good side is that one can see how others have solved various technical issues, the bad of course is that one can also come across the 'sausage making' that has encrusted a 'mature and stable module'.
And Yes, you can do
perldoc -m perldoc
but BE VERY VERY QUITE, it can get way, uh, scary in there.... Big Fanged Beasties roaming around...
ciao drieux
---
-- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
