where is the code?An alpha on CPAN in a couple of weeks, I hope. (-: I wouldn't waste everyone's time with such a big pain if I wasn't making it free! :-)
Since this seems understandable (-: at last :-) I mostly need to finish the CGI example.
your goal is to create a way to build a referee that can be handed a gamestate and a prospective move and it tells you if the move is legal or not?The problem was more modest -- modelling a part of a game called Car Wars. It was quite popular at the end of the 80s and noone ever wrote an implementation for the design rules, but many have certainly tried. The rules have too many exceptions and ugly special cases. Which is the main reason I worked on solving it.
I'll do some examples, but don't really think anyone will use it for what I use it. That is why I try to get the documentation understandable before releasing.
Maybe a type-inferencing language like ML would be more appropriate.You're certainly correct!
I didn't really know what I was doing from the beginning -- this grew organically. I choose Perl mainly because I wanted to find a project with it. If I rewrote this, it wouldn't be in any "normal" language, I think.
I don't know if five or five thousand people will have a use for this. But, as I wrote, when this tool fits well, then it will solve very hard problems.
In reply to Re^2: RFC hierarchic modelling documentation
by BerntB
in thread RFC hierarchic modelling documentation
by BerntB
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |