in reply to Re: CPAN not so comprehensive
in thread CPAN not so comprehensive

Thank you kindly BrowserUk, when you showed it to me, everything seemed to be a bit clearer :). So, documentation can be nested, it's a valuable information.

May i assume that this rule applies to all modules? like when Foo::Bar calls baz method and i did not find (sub?)methods for baz, looking for Foo::Bar::baz is an option?

Question might sound naive, but i am rather skilled in shell scripting/ 8bit assemblers and this whole OO-way of thinking is much abstraction to me. I found it very complicated as you can see on above example...

Replies are listed 'Best First'.
Re^3: CPAN not so comprehensive
by BrowserUk (Patriarch) on Mar 27, 2018 at 05:06 UTC
    May i assume that this rule applies to all modules? like when Foo::Bar calls baz method and i did not find (sub?)methods for baz, looking for Foo::Bar::baz is an option?

    No. Don't assume that. It is entirely down to how the author choses to document (or not!) his code.

    But it certainly does no harm to look for it :)


    With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority". The enemy of (IT) success is complexity.
    In the absence of evidence, opinion is indistinguishable from prejudice. Suck that fhit