Dennis Ruffer wrote: > > On Dec 4, 2007, at 12:33 PM, Anton Ertl wrote: > > It's not yet finished, though: it's not good for multi-processing and > > especially multi-user usage yet. > > Is there anything I can do to test this?
You can test libcc.fs with ./gforth test/libcc.fs Concerning multi-processing and multi-user, it does not make sense to test this before it is supposed to work. > As an aside, is it possible to update the date in the version number > once in a while? It's still sitting at 0.6.9-20070604 which makes it > pretty hard to track what has been installed on any system. I'm not > sure what your current policy is, but a more frequent change would be > useful, from a user's perspective. The policy is that I update the version number when I make a snapshot or release. If you are working from the CVS head, the usual thing is to run cvs -n update to see which files have changed since the last update, or cvs diff -u to see the exact differences. If you are more interested in dates, you can look at the mtimes of the source files to see when they were committed, or at the mtimes of the CVS/Entries files to see when you last checked out some file in that directory. - anton --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
