Re: Re: Inline POD vs. EOF POD

I doubt that very much. Except for use in a classroom, modules are written to be used. Even if the users are developers. Not to be picked apart and their implementation studied.

When it comes to the traditional CPAN module, I'm with you all the way.

But there are other cases; consider the in-house developed program consisting of a number of classes. This is often not a case of just using a stable module or two, but a living piece of code that is indeed being changed, added to, refactored, reimplemented every once in a while.

That was primarily what I was thinking of when stating that inline POD is useful to document interfaces. Not in a "guide" way, but in a "reference" way. If a class needs notes about intention, recommended use, etc. that should of course be part of the docs too.

Comment on Re: Re: Inline POD vs. EOF POD

Replies are listed 'Best First'.
Re: Inline POD vs. EOF POD by Abigail (Deacon) on Jul 11, 2001 at 14:07 UTC
Now you are describing a very specific situation, which is a far cry from your earlier "everyone will use inline POD if the syntax gets changed". But even in this situation, what advantage will POD give you over (block) comments? After all, when you see the formatted POD, you no longer see the code, and I would think that people maintaining the code would like to see the code. -- Abigail	[reply]
Re: Re: Re: Inline POD vs. EOF POD by jplindstrom (Monsignor) on Jul 12, 2001 at 19:51 UTC
Now you are describing a very specific situation, which is a far cry from your earlier "everyone will use inline POD if the syntax gets changed". I don't think it was me saying that, but never mind. The "specific situation" is one that I encounter every day: I author and maintain a number of programs/applications written in Perl. I put common stuff into general CPAN-style modules, but the actual program functionality is always a number of very domain specific classes whose interface needs to be documented. For that I use POD which I think works fine, especially since I also use a POD/module browser that will jump me right into the source when I need that. Writing CPAN modules is another "specific sitation", although a more common one for some people. Again -- the interface needs to be documented, the usage too. The interface should be documented near the implementation, hence inline POD. The usage should be described and explained. EOF or BOF POD is perhaps more natural in this case. The issue of where to place POD (if that's what you like best) is maybe not "either-or", rather "both", since both are needed. New revised personal preference :) Usage: POD Interface: Inline POD Implementation: Perl Comment /J	[reply]