I think Alan Moore wrote:
> 
> 
> In a previous post, I suggested a RHS parser extensibility mechanism where
> upon reaching an extensible set of tokens, the parsing/input stream could be
> passed along to an associated parser. My original post was motivated by
> wanting to do:
> 
> (defrule myRule
>   (a ?count)
>   (b ?datum)
> =>
>   (myParser {some; other; language(); here!}
>   )
> )
> 
> where the token/parser myParser could be registered with Jess.


Indeed, this could be nice. You could accomplish much the same thing
using unmodified Jess and using "" as the delimiters, however. You'd
have to escape "" characters appearing in the other-language code.

> 
> CLIPS had a feature (I think?) where you could validate your "user function"
> input parameters. I don't think it let you parse the input however. I has
> been quite a while.

Yes, CLIPS lets you tell it what the proper argument types are for a
user function when you register it; that's what you're thinking of.


I know that the following is also near and dear to your heart: I've
been starting to think that notation like

(bind ?x ?vec.elementAt(3))

would be nice to have, as opposed to the current

(bind ?x (call ?vec elementAt 3))

The only serious issue regarding this is that currently, a '.' is an
allowed character in a symbol, so tokenizing the above as the separate
tokens '?vec' '.' 'elementAt' would require some context-dependent
parsing. Dots are allowed in symbols only because one user long ago
requested this - they wanted IP addresses like 127.0.0.1 to be
valid symbols. 

If anyone is reading this far down: how important is it that symbols
can contain dots?




---------------------------------------------------------
Ernest Friedman-Hill  
Distributed Systems Research        Phone: (925) 294-2154
Sandia National Labs                FAX:   (925) 294-2234
Org. 8920, MS 9012                  [EMAIL PROTECTED]
PO Box 969                  http://herzberg.ca.sandia.gov
Livermore, CA 94550
---------------------------------------------------------------------
To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]'
in the BODY of a message to [EMAIL PROTECTED], NOT to the
list (use your own address!) List problems? Notify [EMAIL PROTECTED]
---------------------------------------------------------------------

Reply via email to