On Nov 29, 2005, at 1:45, jerry gay wrote:
the parrot directory structure is large and a bit disorganized. let me give you some examples: * build_tools/, util/, and tools/*/ each contain utility perl scripts. these should be grouped together under tools/, which already contains subdirectories
Yes. But first make sure that build_tools contains really all build tools, which it doesn't. tools/dev/cc_flags.pl is AFAIK used during build. OTOH build_tools/list_unjitted.pl is just a tool.
* there are multiple dirs containing C source code (charset, classes, io, etc.) these should be grouped together under src/ * the editor/ directory contains files for text editors and has a generated makefile. there is no reason for this to be a make target. a perl script should be created to replace makefile, and the dir moved with the other tool & utility scripts.
Nope - why a perl script for a make job?
* imcc test files are not grouped with other tests (this is already on my TODO list and should be done RSN.) i propose reorganizing the tree to improve clarity and cohesion. here is an annotated picture of the current tree (extra info <snip>ped as shown.) . trunk +---ast
ast is another builtin parrot compiler BTW.
+---imcc | +---docs
Should be merged into docs/
... of course, a realclean / configure / make test cycle should be done after each change to ensure it has gone smoothly.
... on several different platforms.
thoughts? ~jerry
leo
