Bill,

See
https://github.com/GabrielDosReis/open-axiom/commit/04be6d65c9bae10780f463c23a14922249c187de

I don't know that your specific scenario works out of the box, since
OpenAxiom requires separating build directory from source directory, hence
you might run into load directory issues.
If you have standalone Boot source files, that should work.

-- Gaby


On Sun, Jan 31, 2016 at 6:37 PM, Bill Page <bill.p...@newsynthesis.org>
wrote:

> Gaby,
>
> Thank you very much for the explanation. I understand and appreciate
> that OpenAxiom is moving away from depending on Lisp, I just did not
> know quite how much!  I can live with re-running make. In fact I have
> been doing that and it seems that the dependencies are sufficiently
> fine grained that the cycle does not take very long.  This is probably
> a better a methodology in any case.  In my limited experience it seems
> that Lisp and even Boot in FriCAS makes it a bit too easy to just hack
> away at a problem. :)
>
> Regards,
> Bill Page.
>
> On 31 January 2016 at 20:21, Gabriel Dos Reis
> <g...@integrable-solutions.net> wrote:
> >
> >
> > On Sun, Jan 31, 2016 at 5:10 PM, Bill Page <bill.p...@newsynthesis.org>
> > wrote:
> >>
> >> Gaby,
> >>
> >> I am not quite sure what you mean by "separately load it"?  What I
> >> have in mind is to compile a boot file to Lisp and then load it -
> >> typically replacing some existing code in a running system.
> >
> >
> > OpenAxiom has two ways of handling Boot code:
> >    (1) translate Boot to Lisp -- deprecated
> >    (2) compile Boot to machine code directly -- for more specifically a
> Lisp
> > FASL
> >
> > The preferred method is (2), as the system is minimizing lispisms and
> heavy
> > dependency on Lisp systems.  At this moment, (1) is used only for
> building
> > the Boot translator itself, and is deprecated.  Building the OpenAxiom
> > compiler and/or interpreter is done via (2).
> >
> > My question was whether you wanted the ")read" command to just do (2), or
> > (2) + load the resulting FASL into the running system.
> > OpenAxiom applies more aggressive optimizations than other AXIOM systems.
> > This means that when you modify an existing function and it was inlined
> into
> > some of its callers, then recompiling the boot file might not necessarily
> > give you a consistent result.  I don't know if this is a concern for you.
> > This consistency reason was the primary reason why ")read" for Boot
> script
> > was removed at some point.  I can put it back if you are aware of the
> > consistency problem -- meaning I won't be able to help with consistency
> > problems :-).
> >
> >
> >>
> >> I do this
> >> quite frequently when debugging or testing some limited change in
> >> FriCAS.  I was surprised by the error returned in the following
> >> example:
> >>
> >> (1) -> )read open-axiom/src/interp/format.boot
> >>
> >>    >> System error:
> >>    The function BOOT::BOOT is undefined.
> >>
> >> Bill.
> >>
> >> On 31 January 2016 at 14:23, Gabriel Dos Reis
> >> <g...@integrable-solutions.net> wrote:
> >> > Hi Bill,
> >> > Is the idea that you would like to change a BOOT file, compile it, and
> >> > then
> >> > separately load it?
> >> > Or just read in the interpreted form of a BOOT file?
> >> >
> >> > -- Gaby
> >> >
> >> >
> >> > On Fri, Jan 29, 2016 at 7:56 PM, Bill Page <
> bill.p...@newsynthesis.org>
> >> > wrote:
> >> >>
> >> >> Is there a way to do this in OpenAxiom?  A typical use case is when I
> >> >> am debugging or experimenting with changes to the compiler or
> >> >> interpreter.
> >> >>
> >> >> I tried:
> >> >>
> >> >>     )read xxx.boot
> >> >>
> >> >> but I an error message
> >> >>
> >> >>     (1) -> )read define.boot
> >> >>
> >> >>        >> System error:
> >> >>        The function BOOT::BOOT is undefined.
> >> >>
> >> >>
> >> >>
> >> >>
> ------------------------------------------------------------------------------
> >> >> Site24x7 APM Insight: Get Deep Visibility into Application
> Performance
> >> >> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> >> >> Monitor end-to-end web transactions and take corrective actions now
> >> >> Troubleshoot faster and improve end-user experience. Signup Now!
> >> >> http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
> >> >> _______________________________________________
> >> >> open-axiom-devel mailing list
> >> >> open-axiom-devel@lists.sourceforge.net
> >> >> https://lists.sourceforge.net/lists/listinfo/open-axiom-devel
> >> >
> >> >
> >>
> >>
> >>
> ------------------------------------------------------------------------------
> >> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> >> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> >> Monitor end-to-end web transactions and take corrective actions now
> >> Troubleshoot faster and improve end-user experience. Signup Now!
> >> http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
> >> _______________________________________________
> >> open-axiom-devel mailing list
> >> open-axiom-devel@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/open-axiom-devel
> >
> >
>
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
open-axiom-devel mailing list
open-axiom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/open-axiom-devel

Reply via email to