On Sat, 2007-07-14 at 23:40 -0700, Raoul Duke wrote:
> b) make the docs there 100% right. if that means deleting 90% of it
> that's fine. better to be curt but accurate.
That is almost impossible at the moment. The only way to get
a correct reference and tutorial is to closely integrate them
with the source.
The tutorial actually generates tests that run, so we have
a way to make sure the tutorial examples are real working code
(a literate programming system, interscript, plus build system
support for building and running the tutorial examples automatically
AS PART of the build processes .. which is a lot more than
most packages do.. even the Debian autobuilder is forced
to run all the regression tests :)
The only way to 'explain' the language accurately
is to couple the descriptions directly with the grammar.
That simply wasn't possible until now, with the extensible
user defined grammar.
> c) re-make sure 100% of the tests work for that 'frozen' tip-of-tree.
I usually check all the core tests work on Linux every day:
not every commit, but many of them, and for the others I run
some of the tests before cancelling confidently and out
of boredom waiting.
So the tests SHOULD work, all of them, all the time.
The demos may or may not: they're harder to test because
they're interactive.
> d) re-make sure the install works 100% for your 2 favourite system
> flavours (linux, windows? screw os x? or just say "you are own your
> own, but we'd love to get a mac maintainer").
RF is building a platform independent game so he wants it to
work on OSX (his system) and Windows (his real market).
> e) make sure there are good install docs, even if no other docs at all?
How can you write install docs to cover all situations?
The instructions are simple.. copy the build directory anywhere
you like.
That's it. Of course, you have to know bin/flx is the bash
execution script, and bin/flx.bat is the Windows version of it,
and you have to now how to use it to select the version:
flx --test=DIRECTORY ...
or
export FLX_INSTALL_DIR=where_i_put_felix
flx ...
or
edit where_i_put_flx/flx
# change the hard coded install directory
flx ....
Of course,
make install
should work too .. doesn't it?
> f) don't have to branch SVN every time and merge, but at least make a
> public ann't about the revision # which was last known to work?
They head always works, unless someone (usually me) announces
it is going to be broken. That did happen recently .. the last
time it happened was over a year ago I think. It's very rare,
but it does happen during a major upgrade. This upgrade was
commenced immediately after the last release.
--
John Skaller <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Felix-language mailing list
Felix-language@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/felix-language
