From a language standpoint, I think this is a great solution. As Jonathan
suggests, have a default knowledge base that is referenced by default, with
the option to declare more knowledgebases. Each one can have facts set and
queries exectued seperately. I have only a passing knowledge of Prolog,
We could always go with the Windows API "Critical Section" name. Locked is
probably as good a descriptor, and avoids anything associated with Windows.
Sage
James Mastros skribis 2006-05-31 12:03 (+0100):
> I don't like the name synchronized -- it implies that multiple things
are
> happening at
Hello all,
I'm the student picking up on the translation work lwall started. Since the
perl 5 parser is more or less complete, I've headed straight to the
translation work. I'm going to be taking on the translations a few at a
time, starting with the easiest translations and moving to the more co
"interpolative context" ment the perl 5 side, where the double quotes should
cause interpolation. Maybe not the best phrase to identify it, now that you
mention it.
Sage
On 6/6/06, Aaron Crane <[EMAIL PROTECTED]> wrote:
Sage La Torra writes:
> http://infohos
Just an update:
I've started coding (in haskell, to be used with Pugs). I've got file input,
I've got a data structure for the AST, now I just have to make them play
nicely together. I'll start implementing translations soon, so any other
corrections would be appreciated.
Thanks to everyone who'
On 8/30/06, Jonathan Lang <[EMAIL PROTECTED]> wrote:
Joe Gottman wrote:
> Since a FIRST block gets called at loop initialization time, it seems to
me
> that it would be useful to have a block closure trait, RESUME, that gets
> called at the beginning of every loop iteration except the first. Thu
On 8/31/06, Mark J. Reed <[EMAIL PROTECTED]> wrote:
I anticipate typos galore from the near-collision of names between
"subst" and "substr"; perhaps "replace" would be a better name, even
though
it breaks the mnemonic association with s///?
Perhaps the long name "substitute" would work? While
