RE: [PATCH] .dev files.

Brent Dax wrote:
> Do you really want to see a ten-page discussion of hashing
> algorithms and why the current one was chosen in the middle
> of classes/perlhash.pmc?

I guess that wouldn't bother me as much as it might bother
some other people.


> *That's* the sort of thing the .dev files are for,
> not API documentation.

Well, fine; but then, that's not the sort of doco that needs
to have a 1-to-1 correspondence between source code file and
and doc file.

Furthermore -- why are .dev files not pdd files?
Is it because pdd is *design* while .dev is *implementation*?
If that's the case, then, like I said, having the source and
the doc in separate files, in different directories, makes
keeping them in sync more of a hassle and therefore more
likely to fall through the cracks.  Or "back-burnered".

I wonder what, if anything, XP has to say on this issue.

-- 
JohnDouglasPorter




__________________________________________________
Do You Yahoo!?
Yahoo! Autos - Get free new car price quotes
http://autos.yahoo.com

• [PATCH] .dev files. by Andy Dougherty
• Re: [PATCH] .dev files. by Tanton Gibbs
• Re: [PATCH] .dev files. by John Porter
• Re: [PATCH] .dev files. by Josh Wilmes
• Re: [PATCH] .dev files. by Andy Dougherty
• Re: [PATCH] .dev files. by Nicholas Clark
• Re: [PATCH] .dev files. by John Porter
• Re: [PATCH] .dev files. by Dave Mitchell
• Re: [PATCH] .dev files. by Nicholas Clark
• Re: [PATCH] .dev files. by Dave Mitchell
• Re: [PATCH] .dev files. by John Porter
• RE: [PATCH] .dev files. by Brent Dax
• RE: [PATCH] .dev files. by John Porter
• Re: [PATCH] .dev files. by Tanton Gibbs