Simon Cozens wrote: > Dave Mitchell: > > I'm trying to nip the following in the bud, which is daunting for someone > > trying to work out what's what for the first time. > > > > ls perl-current/ > > I see your point, but I don't think 'ls perl-current/src' is much better. :)
True, but the point is that ls parrot/ *would* be better: Configure.pl MANIFEST README classes/ config/ doc/ pdd/ pod/ src/ (or thereabouts) I'd like it if the src directory only contained zillions of *.[ch] files, and didn't have other random stuff mixed in with it. It really boils down to two things: 1) do we want to group similar things into directories (src, config, doc etc), 2) do we want all the directories at the same level, or should the the src be the parent directory of the others. I guess we agree on (1), and disagree on (2). Another way of thinking about it is that in the final parrot, we may end up with several binaries (parrot.exe, optimiser.exe etc) plus libraries, and we may want a separate src dir for each. > If we're going to do anything I think we should separate the generated > files from the generators. Possibly even have a build subdirectory. I'm all in favour in principle. Might not be practical if/until we replace make with something better.
