I agree with this; however, I also think it would be nice to have it all in one place. It's a nuisance to have to open every file just to see what it is. By the time I figure out what the 60th file does, I've forgotten what the first does. It would be nice to have the information at the top of the file and then have a program pull it and create a separate file...that way they are always in sync.
Tanton ----- Original Message ----- From: "Sean O'Rourke" <[EMAIL PROTECTED]> To: "mark sparshatt" <[EMAIL PROTECTED]> Cc: "perl6-internals" <[EMAIL PROTECTED]> Sent: Friday, October 04, 2002 11:17 AM Subject: Re: Parrot file list > On Fri, 4 Oct 2002, mark sparshatt wrote: > > Basically I'd like to know if there's any sort of listing that gives a > > general description of what each file is used for. > > > > If there isn't, I've started making some notes of my own and if anyone else > > thinks this would be useful then I can type them up in POD format and send > > them in. > > I'd actually like to see this sort of info at the top of each file, > perhaps in the overview section. That way it's less likely to drift away > from reality when existing files are changed or new ones are added. For > files where this is not possible (e.g. the pdds), maybe a per-directory > README or WTFISTHIS could be used instead. Just a thought -- I have > enough trouble keeping the manifest in sync ;). > > /s > > >
