Martin Rubey <[EMAIL PROTECTED]> writes:

[...]

| > I can see how this can be limiting in some cases, but I suspect it makes an
| > interesting language design choice.  A fundamental question (to me) is:
| > beside optimizations such as the one you want, is there any programming
| > technique that benefit a lot from that?
| 
| Hm?  This behaviour -- as currently implemented and as explained by yourself
| and Ralf -- actually *allows* the optimization.  No, I do not want other
| behaviour.  I was just trying to say that I could live with both ways.

I suspect I did not explain myself clearly.  

I acknowledge the current implementation allows the transformation.
The debate over the last couple of weeks was whether it was intended
or whether it was a desirable behaviour.

The question I'm asking now is: Beside the optimization (which I'm not
dismissing), are there any programming techniques (or classes of
algorithms) that benefit from that choice (as opposed to having
virtual functions)?  I'm curious.

[...]

| Finally, another question: the code in comp.lisp looks really hard to
| understand for me, although I admit that I didn't really try.  Wouldn't it be
| better to do away with it and produce ANSI Common Lisp in the code.lsp?

Although the code in comp.lisp stands in the way of little things, it
is not the main bottleneck.  It can be relatively easily be extended
or excised (it has duplicates in other parts of the system).  Its main
job is to convert `opcodes' to digestible ordinary Lisp.

In fact, my view is that once we have produced a Lisp code, we have
lost hope of getting the code faster.  Spad is strongly typed.  We
should not first generate Lisp and then try to optimze the Lisp.


| Or did
| I misunderstand something here?  Is comp.lisp another optimization pass?

There isn't much optimization there; just bucnh of macro expansions
and variable declaration hosting.

-- Gaby

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
open-axiom-devel mailing list
open-axiom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/open-axiom-devel

Reply via email to