Hi Mark,

Regarding your introspection utility:

It looks like this utility is unable to parse the pattern syntax of a rule LHS
(Left Hand Side). I suspect it may not be able to parse anything that doesn't
look syntactically like lisp:  is this correct?

Fortunately, you may only be missing a few operators to make your parser more
complete:
    The boolean operators " & | ~ ", functions and their place holder " : "
    (See "JESS Language" Chapter 2  Basic Patterns for an explanation of what
you colorfully describe as 'cartoon swearing'!)

As I mentioned I'm not a lisp programmer, so I don't know exactly what's
missing.

Hope you do pick it up again, though - performing introspection on rule
meta-data could really help those of us with substantial rule sets. But be
cautioned that this method will be limited to clips source code for fact
assertion sources  (facts can potentially be generated from java objects as
well).

If you do any more with this utility, let us know.

Thanks,

Jack

[EMAIL PROTECTED] wrote:

> Quoting Jack Kerkhof <[EMAIL PROTECTED]>:
>
> > Hi again Mark
> >
> > OK, here's question 3++:
> >
> > Got myself  clisp  from Gnu, compiled and loaded your program. So far
> > so
> > good.
> >
> > But the program seems to trip up parsing clips syntax ?T&:
>
> I don't use any of that shorthand because it looks too much like
> line noise or cartoon swearing to make any sense.
>
> The utility only deals with as much JESS syntax and functionality
> as I've actually used.  Not having done anything with JESS in a
> few months, I don't feel much incentive to extend it.  Sorry
> about that.
>
> I don't recall which of all those punctuation characters are
> special to JESS.  It might require a special CommonLisp read table
> to be able to get them read in.  See chapter 23 of the CommonLisp spec
>
>     http://www.xanalys.com/software_tools/reference/HyperSpec/Body/23_.htm
>
> for information about extending the lisp reader for this.  You might need
> to start with a more rigorous description of the special colon syntax
> before you proceed further.  You would then need to make a new read table
> for use by the utility which treated the colon character not as the lisp
> package prefix character but rather as a symbol constituent character
> or as a reader macro character.  I don't think getting this to work will
> be easy.
>
> Alas, my computer is in the shop so I'm unable to look at any of this
> until it comes back.
> ... :


--------------------------------------------------------------------
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