John Porter:
# Tanton Gibbs wrote:
# > . . . That saves a person digging through
# > the .c file to find what they are looking for.
# > Perhaps we could automatically update the .dev
# > file with the POD found in the .c file?
#
# As someone else has already said, a better place
# for the .dev information might be inside the .c
# file itself.
# I for one find the separation unnatural,
# uncustomary, and de-sync-prone.
# Frankly I just don't see what it buys us.
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? *That's* the sort of thing the .dev files are
for, not API documentation. I agree that API docs should be in the
source file, but not much more than that.
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding regexen Configure)
He who fights and runs away wasted valuable running time with the
fighting.
