Terrance Swift writes:
> load_dync reads data canonically, which means its reader is very fast, but
> rather picky. So it considers
>
> a(1,b([])).
>
> canonical, but
>
> a(1,b([ ])).
>
> not canonical. load_dyn has a reader that handles general prolog and
> hilog terms (at least
> as well as XSB's reader handles prolog terms :-) but is somewhat slower
> as a result. David is the main author of load_dync, so let's see if he
> considers it a bug or a feature.
Yes, Terry has it right. I would consider [ ] to be noncanonical. (I
actually remember that this was a bug in read that we had to go into
and fix.) [] is actually an atom, not a list. So allowing [ ]
introduces the idea of an atom with a blank in it. That's messy to
handle in the code, and not a simple lexical idea. So this is a
feature, not a bug:-).
> Depending on what you are doing, load_dync can load a lot of code very
> quickly -- We've had applications of XSB where load-dyncing lots of CDF
> code in XSB
> took only a few seconds. But multi-file with dynamic code is a reasonable
> request, and I don't think it should be too hard to incorporate
> into load_dyn(c). Again, let's see what David says, but I'm sure we can
> find some solution for you.
I've explained in a previous message my understanding of multifile and
dynamic code. As Terry says, we can find a solution, even if it's not
multifile.
Regards,
-David
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
|
