Re: BRL with kawa 1.8.91

[Per Bothner <per at bothner dot com>]

On 05/12/2009 07:53 AM, Dan Stanger wrote:
> My brl page now contains [(symbol->string 'b)] .
> Here is a partial backtrace after the call to atEvalLevel.lambda1$X
> (x.brl .
>    [1] atEvalLevel.lambda1$X (x.brl:1)
>    [2] atEvalLevel.apply (null)
>    [3] gnu.mapping.CallContext.runUntilDone (CallContext.java:251)
>    [4] gnu.mapping.CallContext.runUntilValue (CallContext.java:315)
>    [5] gnu.expr.ModuleWithContext.applyN (ModuleWithContext.java:209)
>
> After 2 step up commands I am at:
> Step completed: "thread=main", gnu.mapping.CallContext.runUntilValue(),
> line=31
>   bci=30
>
> main[1] print vst
>   vst = "[0, ]"
>
> Shouldn't vst contain [1,"b"] or something like that?

I don't know, since I don't know what is happening.  Setting:
    Compilation.debugPrintExpr = true;
and/or
    Compilation.debugPrintFinalExpr = true;
will print (to the error port) the parsed expressions.
Setting:
  ModuleExp.dumpZipPrefix = "kawa-zip-dump-";
will generate .zip files of the generated classes.

But this looks like the old "eval-based" implementation of BRL.
That implementation will be harder to debug, because it makes
a lot of eval calls.  The BRL re-implemention that ships with
Kawa handles your example just fine, both as a standalone file:
   kawa --brl -f x.brl
and in Tomcat.

I really and most strongly recommend that you spend as little
time as possible on the old eval-based implementation.  Instead,
concentrate on bringing the new integrated implementation (the
one that is part of the Kawa code-base) up to your needs.  That
will be easier in the long run - and possibly in the short run,
as I can help more easily.  Having BRL be part of the Kawa
distribution (except perhaps for some optional add-on libraries)
will avoid the kind of incompatibilities we're seeing.

Or have you tried and given up on that?  Perhaps you're concerned
about hard-to-fix incompatibilities between the old implementation
and the Kawa implementation?  If so, I'd like to understand the
issues.
--
	--Per Bothner
per@bothner.com   http://per.bothner.com/