On Mon, 2007-03-26 at 19:27 -0700, Erick Tryzelaar wrote:
> skaller wrote:
> > Maybe we need a
> >
> > test/newbugs/
> >
> > directory where we can just commit new files, and move
> > the codes into the test suite later.
> >
>
> Probably the best idea. Probably shouldn't be that hard to integrate
> into the build system either.
>
> How likely do you think things will actually rolled back in? If it
> doesn't happen that often maybe we should just pull all the tests out of
> iscr.
That would stuff up the iscr based dependency checking.
I mean most of the Ocaml code doesn't have to be generated.
But if we pull it out, how do we know when to trigger
a rebuild?
Ocaml 3.10 solves this problem with a new tool, ocamlbuild.
> The only thing with that is that it'd take a little engineering to
> deal with test categories. Oh, and cleaning up all the extra files that
> felix generates. We don't have a way to say "generate all the files in
> this directory" to flxg, do we?
no, but that needs to be done. Been meaning to, because if the
*.flx is in a read only directory things aren't nice.
The idea is a stack of directories: all write go to the top of stack.
Reads search down the stack.
So you can shadow any file, eg flx.flxh, with an intermediate
directory. It's a purely functional design.
So instead of
-Ilib
where lib is a directory we have
flxg -I[/usr/lib/felix/lib; /usr/local/lib/felix/lib; \
~/myfelixlib; ./lib; ~/.flx_cache] ....
--
John Skaller <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Felix-language mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/felix-language
