Hi, On Wednesday 07 April 2004 08:50, Leopold Toetsch wrote: > - runtime/parrot/*/ This directory does only include generated files, doesn't it? > - library/ Maybe move it to runtime/library? We can also create a runtime/t/ (or t/runtime) where the library tests can go to.
> 1) We should probably decide to use just one for simplicity. ack > 2) Library search paths and appropriate helper functions inside Parrot > are still needed. What about an PMC array? Each PMC can then represent a directory Parrot does the C equivalent of "set file, dir[name]", if the file returned is a ParrotIO it is used to read the library file. > 3) we need some scheme to organize lib paths What about runtime/parrot for parrot's generated files runtime/library for PIR/PASM libs working "out of the box" parrot directories like runtime/perl6, runtime/tcl... for other languages and everything that needs a special backend to be usable the backend can just add the runtime path to parrot's library path > 4) Library testing is needed as well indeed. is it okay to use (e.g. the streams) examples as test basis? A test can then simply include the example code and check its output. This way, we know that the examples are working and do not have duplicated code. On the other hand, it can make problems if someone modifies an example and then runs the tests. jens
