Q: How do I structure a library for testing?

Austin Hastings Austin_Hastings at Yahoo.com
Wed Jul 1 15:11:24 UTC 2009

So I've got this programming language, Close, that I'm implementing atop 
And the language setup script has given me a directory tree:

.... - build
.... - docs
.... - src
.... ... - builtins
.... ... - parser
.... - t

That's all well and good, and I've made some nice progress implementing 
my language. But now I want to add a "library" to the mix. Actually, 
more than one. And I think that my library should have some tests written.
So how should I structure this? Should I commingle the source and tests 
with the compiler stuff, and let the makefile sort them out? Should I 
create an entirely separate project? Is there some structure that is 
already generally agreed-upon that I am not aware of?
Also, how do I structure library code for deployment to an installed 
parrot? I've been assuming that "library/close" will work for the close 
runtime library, but if I just want to deliver a Foo library, what 
should that look like, deployment-to-an-installed-parrot-wise?

More information about the parrot-dev mailing list