Re: [Axiom-developer] concatenate and bit-vector

--- [EMAIL PROTECTED] wrote: > Steve, > > In order to move from MacLisp to VMLisp and then to pre-common lisp > and then to common lisp (and now to ansi) one of two possible > approaches can be taken. The first approach is to emulate the > semantics of the original system in the new system. The

[Axiom-developer] bootstrap Meta/Boot

> Derive Derive is a fantastic program and often outperformed everything else. It is historically interesting, in the "Newton's Notebooks" sense. I have spent the last few months trying to convince TI to either release the original derive lisp code (which they no longer use) or to write a "d

Re: [Axiom-developer] aldor stream oddities

Franz Lehner <[EMAIL PROTECTED]> writes: > dear all, > > > "The important thing is to escape the keyword generator by prefix with _." > thanks a lot for your quick replies and solutions. > I am trying to put together some functions to manipulate moment sequences and > got stuck constructing the z

[Axiom-developer] bootstrap Meta/Boot

>> It hardly matters. The "new world" allows everyone to do whatever >> suits their mood by creating their own branch. This will eventually >> undermine the whole effort rendering the language debate mute. > It may allow arbitrary branches/forks, but the odds of any of them > creating a successful

[Axiom-developer] bootstrap Meta/Boot

(ah, forth. i do so love forth) Scheme is quite nice. My son implemented and sells a PHP compiler in scheme. Scheme has two flaws from my point of view. A minor flaw is that I end up implementing half of common lisp in scheme, and badly at that. A major flaw is that scheme broke the correspondenc

[Axiom-developer] Re: bootstrap Meta/Boot

[EMAIL PROTECTED] wrote: >> But does it really need so many sub-languages? > > Well, that's a religious question. > > Some on the wailing list feel that Meta and Boot should be recovered, > made strongly typed, and closer to the algebra language. On the plus > side it will be claimed that these

[Axiom-developer] Re: bootstrap Meta/Boot

[EMAIL PROTECTED] wrote: >> the one that I think has the strongest legs is Erlang > > Funny you should mention that as I'm half way thru the new Erlang book. > This model, if not the language itself, is a perfect vehicle for an > implementation of provisos (much discussed on this list). Using clos

[Axiom-developer] bootstrap Meta/Boot

> the one that I think has the strongest legs is Erlang Funny you should mention that as I'm half way thru the new Erlang book. This model, if not the language itself, is a perfect vehicle for an implementation of provisos (much discussed on this list). Using closures, SBCL threads, and some trans

[Axiom-developer] bootstrap Meta/Boot

> But does it really need so many sub-languages? Well, that's a religious question. Some on the wailing list feel that Meta and Boot should be recovered, made strongly typed, and closer to the algebra language. On the plus side it will be claimed that these are "higher level" (or could be made i

Re: [Axiom-developer] Re: bootstrap Meta/Boot

Gabriel Dos Reis wrote: > In fact that is open to debate, by reality check. The only "good" > Common Lisp compiler I know freely available is SBCL, and we don't > support it right now. And Common Lisp actually gives you very little > support to write useful programs. Well ... SBCL is a re-write

Re: [Axiom-developer] Re: bootstrap Meta/Boot

"M. Edward (Ed) Borasky" <[EMAIL PROTECTED]> writes: [...] | As a user who can't quite find the time to get involved with Axiom on a | deeper level, I must say I find the plethora of languages in the Axiom | development scheme quite daunting. Let's see: there's Axiom, Boot, SPAD, | Aldor *and* C

Re: [Axiom-developer] Re: bootstrap Meta/Boot

Gabriel Dos Reis wrote: > "Bill Page" <[EMAIL PROTECTED]> writes: > > | On 8/9/07, Tim Daly wrote: > | > > | > In the IBM/NAG days you needed a running Axiom to build Axiom. > | > > | > | I believe that is one of the things that allowed Axiom to become so > | advanced so quickly (relatively speak

Re: [Axiom-developer] Simon Peyton-Jones video on the "threshold of immortality" (and Haskell)

"Bill Page" <[EMAIL PROTECTED]> writes: | Talk posted by Bruce Stewart: | | http://beautifulcode.oreillynet.com/2007/08/oscon_video_of_simon_peyton_jo.php | | Slides: | | http://conferences.oreillynet.com/presentations/os2007/os_peytonjones.pdf | | I think this energetic talk is important at a

Re: [Axiom-developer] Re: bootstrap Meta/Boot

"Bill Page" <[EMAIL PROTECTED]> writes: | On 8/9/07, Tim Daly wrote: | > | > In the IBM/NAG days you needed a running Axiom to build Axiom. | > | | I believe that is one of the things that allowed Axiom to become so | advanced so quickly (relatively speaking). Axiom's library code is | highly cir

[Axiom-developer] Re: numberOfEmptySlots

On Thu, 9 Aug 2007, [EMAIL PROTECTED] wrote: | The NE occurs in boot code. Yes. | Perhaps the author meant to use the infix form NE? which would be equivalent to ^=, e.g. not equal. Why would that be correct? Hmm. Looking at the code, it is comparing lists and x is taken from cache, then

[Axiom-developer] Simon Peyton-Jones video on the "threshold of immortality" (and Haskell)

Talk posted by Bruce Stewart: http://beautifulcode.oreillynet.com/2007/08/oscon_video_of_simon_peyton_jo.php Slides: http://conferences.oreillynet.com/presentations/os2007/os_peytonjones.pdf I think this energetic talk is important at a number of levels, independently of the specific subject of

[Axiom-developer] numberOfEmptySlots

The NE occurs in boot code. Perhaps the author meant to use the infix form NE? Tim ___ Axiom-developer mailing list Axiom-developer@nongnu.org http://lists.nongnu.org/mailman/listinfo/axiom-developer

[Axiom-developer] concatenate and bit-vector

I plan to rewrite functions into ANSI as I encounter them so, no, I have no objections to a reorganization. Tim ___ Axiom-developer mailing list Axiom-developer@nongnu.org http://lists.nongnu.org/mailman/listinfo/axiom-developer

[Axiom-developer] Re: bootstrap Meta/Boot

On 8/9/07, Tim Daly wrote: > > In the IBM/NAG days you needed a running Axiom to build Axiom. > I believe that is one of the things that allowed Axiom to become so advanced so quickly (relatively speaking). Axiom's library code is highly circularly-dependent as a result. This structure makes Spad

Re: [Axiom-developer] numberOfEmptySlots

Gabriel Dos Reis <[EMAIL PROTECTED]> writes: | Consider the following function from src/interp/clam.boot: | | numberOfEmptySlots cache== | count:= (CAAR cache ='$failed => 1; 0) | for x in tails rest cache while NE(x,cache) repeat | if CAAR x='$failed then count:= count+1 |

[Axiom-developer] numberOfEmptySlots

Consider the following function from src/interp/clam.boot: numberOfEmptySlots cache== count:= (CAAR cache ='$failed => 1; 0) for x in tails rest cache while NE(x,cache) repeat if CAAR x='$failed then count:= count+1 count The SBCL type checker does not like it beca

Re: [Axiom-developer] Lisp in Small Pieces

[EMAIL PROTECTED] writes: | Lisp in Small Pieces, a fantastically well done literate document, | managed to beat out Harrry Potter on Amazon. And it is selling for $4. Well, that certainly is an order of magniture smaller than how much I payed ten years ago -- French version. -- Gaby _

[Axiom-developer] Re: concatenate and bit-vector

Tim, Documentation would certainly help the current strategy, however, I believe that ANSI cl is really the only Lisp variant of importance to Axiom nowadays. Despite the fact that it is certainly more error-prone (and thus difficult) to rewrite everything using CL idioms / semantics I am still i

[Axiom-developer] Lisp in Small Pieces

Lisp in Small Pieces, a fantastically well done literate document, managed to beat out Harrry Potter on Amazon. And it is selling for $4. Tim ___ Axiom-developer mailing list Axiom-developer@nongnu.org http://lists.nongnu.or

[Axiom-developer] Re: concatenate and bit-vector

On Thu, 9 Aug 2007, Stephen Wilson wrote: | [EMAIL PROTECTED] writes: | | > Steve, Gaby, | > | > The semantics of concat are those of vmlisp. | > | > It might be possible to prove that concat is never called with | > bit-vector semantics. The subtle part is to prove that it can't | > occur in g

[Axiom-developer] concatenate and bit-vector

Steve, In order to move from MacLisp to VMLisp and then to pre-common lisp and then to common lisp (and now to ansi) one of two possible approaches can be taken. The first approach is to emulate the semantics of the original system in the new system. The second approach is to prove that the new

[Axiom-developer] Re: concatenate and bit-vector

[EMAIL PROTECTED] writes: > Steve, Gaby, > > The semantics of concat are those of vmlisp. > > It might be possible to prove that concat is never called with > bit-vector semantics. The subtle part is to prove that it can't > occur in generated code (e.g. algebra). A generalization of 'concat mi

[Axiom-developer] Re: concatenate and bit-vector

On Thu, 9 Aug 2007, Stephen Wilson wrote: | I understand that concat is a bit of a misnomer in CL terms since | | (concatenate 'string "FOO-" 'bar) | | fails. Of course: | | (concat "FOO-" 'bar) | | works, under both #+AKCL and #-AKCL varients. They do not seem | inconsistant to me, nor

[Axiom-developer] Re: concatenate and bit-vector

Gabriel Dos Reis <[EMAIL PROTECTED]> writes: > On Thu, 9 Aug 2007, Stephen Wilson wrote: > > | Gabriel Dos Reis <[EMAIL PROTECTED]> writes: > | > | > On Thu, 9 Aug 2007, Stephen Wilson wrote: > | > > | > | Am I missing something? > | > > | > Did you try > | > > | >(concatenate 'string "fo

Re: [Axiom-developer] Re: concatenate and bit-vector

Stephen Wilson <[EMAIL PROTECTED]> writes: | Gabriel Dos Reis <[EMAIL PROTECTED]> writes: | | > On Thu, 9 Aug 2007, [EMAIL PROTECTED] wrote: | > | > | Steve, Gaby, | > | | > | The semantics of concat are those of vmlisp. | > | | > | It might be possible to prove that concat is never called wit

[Axiom-developer] Re: concatenate and bit-vector

On Thu, 9 Aug 2007, Stephen Wilson wrote: | Gabriel Dos Reis <[EMAIL PROTECTED]> writes: | | > On Thu, 9 Aug 2007, Stephen Wilson wrote: | > | > | Am I missing something? | > | > Did you try | > | >(concatenate 'string "foo" 'bar) | > | > in SBCL, for example? | | I dont have to. 'bar is

[Axiom-developer] Re: concatenate and bit-vector

Gabriel Dos Reis <[EMAIL PROTECTED]> writes: > On Thu, 9 Aug 2007, Stephen Wilson wrote: > > | Am I missing something? > > Did you try > >(concatenate 'string "foo" 'bar) > > in SBCL, for example? I dont have to. 'bar is not a sequence. 'concat excepts string designators. 'bar is a str

[Axiom-developer] getrulefunlists

Tim -- Yet one more. Consider the routine GETFUNLISTS from src/interp/parsing.lisp: (defun getrulefunlists (rootfun rs) (let* ((metapfx (or (get rootfun 'metapfx) "")) (mainfun (internl metapfx (pname rootfun))) (mainfunstr (pname mainfun)) (flnam (internl mainf

[Axiom-developer] Re: concatenate and bit-vector

On Thu, 9 Aug 2007, Stephen Wilson wrote: | Am I missing something? Did you try (concatenate 'string "foo" 'bar) in SBCL, for example? -- Gaby ___ Axiom-developer mailing list Axiom-developer@nongnu.org http://lists.nongnu.org/mailman/listinfo/a

[Axiom-developer] Re: concatenate and bit-vector

Gabriel Dos Reis <[EMAIL PROTECTED]> writes: > On Thu, 9 Aug 2007, [EMAIL PROTECTED] wrote: > > | Steve, Gaby, > | > | The semantics of concat are those of vmlisp. > | > | It might be possible to prove that concat is never called with > | bit-vector semantics. The subtle part is to prove that i

[Axiom-developer] bootstrap Meta/Boot

Bill writes: > You probably know where my sympathy lies. I strongly believe that Tim > is right: "This code is not part of the bootstrap but needs to be at > some point." and I object to the continuing trend to reduce everything > to Lisp. In the IBM/NAG days you needed a running Axiom to build A

[Axiom-developer] Re: newrule from metalex.lisp

On Thu, 9 Aug 2007, [EMAIL PROTECTED] wrote: | Gaby, | | Thanks for the explanation. Now the change makes sense. | | Tim wrote: | >> I see no diff-Naur patch against silver | | Gaby wrote: | > I leave this up to you and for another time. | | Why? Because I suspected that once we have identifi

Re: [Axiom-developer] aldor stream oddities

On 8/9/07, Franz Lehner wrote: > dear all, > > > "The important thing is to escape the keyword generator by prefix with _." > thanks a lot for your quick replies and solutions. > I am trying to put together some functions to manipulate moment sequences > and got stuck constructing the zero element.

[Axiom-developer] Re: concatenate and bit-vector

On Thu, 9 Aug 2007, [EMAIL PROTECTED] wrote: | Steve, Gaby, | | The semantics of concat are those of vmlisp. | | It might be possible to prove that concat is never called with | bit-vector semantics. The subtle part is to prove that it can't | occur in generated code (e.g. algebra). I'm sorry b

[Axiom-developer] concatenate and bit-vector

Steve, Gaby, The semantics of concat are those of vmlisp. It might be possible to prove that concat is never called with bit-vector semantics. The subtle part is to prove that it can't occur in generated code (e.g. algebra). Tim ___ Axiom-develope

Re: [Axiom-developer] aldor stream oddities

dear all, "The important thing is to escape the keyword generator by prefix with _." thanks a lot for your quick replies and solutions. I am trying to put together some functions to manipulate moment sequences and got stuck constructing the zero element. Am I right that there is no sequence do

Re: [Axiom-developer] Re: metalex change

Gabriel Dos Reis <[EMAIL PROTECTED]> writes: > On Thu, 9 Aug 2007, Stephen Wilson wrote: > > | Possibly the only sensible semantics would be to have 'concat require > | all its arguments to be of the same type T s.t. (subtype T 'sequence) > | returns true, and then just call (concatenate T args).

Re: [Axiom-developer] Re: metalex change

On Thu, 9 Aug 2007, Stephen Wilson wrote: | Possibly the only sensible semantics would be to have 'concat require | all its arguments to be of the same type T s.t. (subtype T 'sequence) | returns true, and then just call (concatenate T args). I'm fine with this. -- Gaby ___

Re: [Axiom-developer] Re: metalex change

Gabriel Dos Reis <[EMAIL PROTECTED]> writes: > On Thu, 9 Aug 2007, Stephen Wilson wrote: > > | Gabriel Dos Reis <[EMAIL PROTECTED]> writes: > | > Also, if the function expects strings, we should give it a string. > | > | Although not documented as such, it is likely that > | system:string-concat

RE: [Axiom-developer] Re: newrule from metalex.lisp

On Thu, 9 Aug 2007, Weiss, Juergen wrote: | Hi, | | There should be only one parse - for sure. The old one does | not support rules for the interpreter. The bootstrap of | the old parser generator is another difficulty. With at least | the possibility to use Aldor as the new compiler there | are

RE: [Axiom-developer] Re: newrule from metalex.lisp

Hi, There should be only one parse - for sure. The old one does not support rules for the interpreter. The bootstrap of the old parser generator is another difficulty. With at least the possibility to use Aldor as the new compiler there are quite a few arguments in favor of the new parser. It is s

Re: [Axiom-developer] Re: metalex change

Stephen Wilson <[EMAIL PROTECTED]> writes: | Stephen Wilson <[EMAIL PROTECTED]> writes: | | > Gabriel Dos Reis <[EMAIL PROTECTED]> writes: | > > Also, if the function expects strings, we should give it a string. | > | > Although not documented as such, it is likely that | > system:string-concate

Re: [Axiom-developer] Re: metalex change

On Thu, 9 Aug 2007, Stephen Wilson wrote: | Gabriel Dos Reis <[EMAIL PROTECTED]> writes: | > Also, if the function expects strings, we should give it a string. | | Although not documented as such, it is likely that | system:string-concatenate is designed to take string designators as | arguments

[Axiom-developer] SPECIALCASESYNTAX

Tim -- Speaking of meta meta and friends, the SBCL compiler chokes on the following from newaux.lips (defun SPECIALCASESYNTAX () (OR (AND (char= TOK '#\#) (DIGITP CHR (defun TERMINATOR (CHR) (member CHR '(#\ #\( #\) #\. #\; #\, #\Return)) :test #'char=) The problem is that

Re: [Axiom-developer] Re: metalex change

Stephen Wilson <[EMAIL PROTECTED]> writes: > Gabriel Dos Reis <[EMAIL PROTECTED]> writes: > > Also, if the function expects strings, we should give it a string. > > Although not documented as such, it is likely that > system:string-concatenate is designed to take string designators as > arguments

Re: [Axiom-developer] Re: metalex change

Gabriel Dos Reis <[EMAIL PROTECTED]> writes: > Also, if the function expects strings, we should give it a string. Although not documented as such, it is likely that system:string-concatenate is designed to take string designators as arguments instead of `just' strings. This is a fairly common Lis

Re: [Axiom-developer] Re: newrule from metalex.lisp

On 8/9/07, Weiss, Juergen wrote: > In principle metalex.lisp is used to generate fnewmeta.lisp > from fnewmeta.meta (and metameta.lisp from metameta.meta). > metameta.meta is a parser generator written in itself. The > grammar of the old parser (for the SPAD compiler) is > defined in the file fnewm

RE: [Axiom-developer] Re: newrule from metalex.lisp

On Thu, 9 Aug 2007, Weiss, Juergen wrote: | In principle metalex.lisp is used to generate fnewmeta.lisp | from fnewmeta.meta (and metameta.lisp from metameta.meta). | metameta.meta is a parser generator written in itself. The | grammar of the old parser (for the SPAD compiler) is | defined in the

[Axiom-developer] Re: metalex change

On Thu, 9 Aug 2007, [EMAIL PROTECTED] wrote: | Gaby, | | (test 'rule1) | | eventually does a call to strconc, a vmlisp function. | The strconc function is defined in vmlisp.lisp as | | (define-function 'strconc #'concat) | | The concat function is defined in vmlisp.lisp as a call to | |

[Axiom-developer] Re: metalex change

On Thu, 9 Aug 2007, [EMAIL PROTECTED] wrote: | Gaby, | | Actually, we're both incorrect. The argument is missing a quote. Why is it a quote when strconc is defined as synonymous to concat (see vmlisp.lisp) and concat itself is defined as #-AKCL (defun concat (a b &rest l) (let ((ty

[Axiom-developer] metalex change

Gaby, Actually, we're both incorrect. The argument is missing a quote. Tim ___ Axiom-developer mailing list Axiom-developer@nongnu.org http://lists.nongnu.org/mailman/listinfo/axiom-developer

[Axiom-developer] metalex change

Gaby, (test 'rule1) eventually does a call to strconc, a vmlisp function. The strconc function is defined in vmlisp.lisp as (define-function 'strconc #'concat) The concat function is defined in vmlisp.lisp as a call to (system:string-concatenate a b) If you call: (strconc "PARSE-" '

RE: [Axiom-developer] Re: newrule from metalex.lisp

In principle metalex.lisp is used to generate fnewmeta.lisp from fnewmeta.meta (and metameta.lisp from metameta.meta). metameta.meta is a parser generator written in itself. The grammar of the old parser (for the SPAD compiler) is defined in the file fnewmeta.meta. Seems that someone did not lik

Re: [Axiom-developer] macro STEP

On Thu, 9 Aug 2007, Stephen Wilson wrote: | Hi Gaby, | | Gabriel Dos Reis <[EMAIL PROTECTED]> writes: | | > Tim -- | > | > I believe Spad defines the macro STEP (for iteration purposes, like COLLECT). | > I'm unable to locate it right now. Do you happen to know where it is defined? | | It

Re: [Axiom-developer] macro STEP

Hi Gaby, Gabriel Dos Reis <[EMAIL PROTECTED]> writes: > Tim -- > > I believe Spad defines the macro STEP (for iteration purposes, like COLLECT). > I'm unable to locate it right now. Do you happen to know where it is > defined? It has been a while since I looked at this, but I have a vivid re

[Axiom-developer] macro STEP

Tim -- I believe Spad defines the macro STEP (for iteration purposes, like COLLECT). I'm unable to locate it right now. Do you happen to know where it is defined? -- Gaby ___ Axiom-developer mailing list Axiom-developer@nongnu.org http://lists.non

Re: [Axiom-developer] Re: newrule from metalex.lisp

Gabriel Dos Reis <[EMAIL PROTECTED]> writes: > On Thu, 9 Aug 2007, [EMAIL PROTECTED] wrote: > > | Gaby, > | > | > The routine NEWRULE from metalex.lisp contains the following: > | > > | > (test Rule1) > | > > | > That line should read > | > > | > (test "RULE1") > | > | I don't know where metale

[Axiom-developer] newrule from metalex.lisp

Gaby, Thanks for the explanation. Now the change makes sense. Tim wrote: >> I see no diff-Naur patch against silver Gaby wrote: > I leave this up to you and for another time. Why? Tim ___ Axiom-developer mailing list Axiom-developer@nongnu.org h

[Axiom-developer] Re: newrule from metalex.lisp

On Thu, 9 Aug 2007, [EMAIL PROTECTED] wrote: | Gaby, | | > The routine NEWRULE from metalex.lisp contains the following: | > | > (test Rule1) | > | > That line should read | > | > (test "RULE1") | | I don't know where metalex is used anymore. If metalex is no longer used, then we should just r

[Axiom-developer] newrule from metalex.lisp

Gaby, > The routine NEWRULE from metalex.lisp contains the following: > > (test Rule1) > > That line should read > > (test "RULE1") I don't know where metalex is used anymore. The meta language was removed years ago and rewritten into lisp. The zips/meta.tar file is the last remaining evidence.

[Axiom-developer] newrule from metalex.lisp

The routine NEWRULE from metalex.lisp contains the following: (test Rule1) That line should read (test "RULE1") -- Gaby ___ Axiom-developer mailing list Axiom-developer@nongnu.org http://lists.nongnu.org/mailman/listinfo/axiom-developer

[Axiom-developer] InteractiveMode

The variable InteractiveMode used in function postError (postpar.boot) is a typo for $InteractiveMode. -- Gaby ___ Axiom-developer mailing list Axiom-developer@nongnu.org http://lists.nongnu.org/mailman/listinfo/axiom-developer

Re: [Axiom-developer] aldor stream oddities

Hello, I was about to finish my answer, (see below) but the "_"-trick is by far better. Ralf http://wiki.axiom-developer.org/[EMAIL PROTECTED] Hi Franz, On 08/09/2007 04:07 PM, Franz Lehner wrote: > Hello, > > is there a way to get hold of generate$Stream using the aldor > compiler? I sp

Re: [Axiom-developer] aldor stream oddities

On 8/9/07, Franz Lehner <[EMAIL PROTECTED]> wrote: > Hello, > > is there a way to get hold of generate$Stream using the aldor compiler? > I spent quite some time until figuring out that generate is probably > a keyword in aldor (I could not check as the aldor site seems to be down) > and this cause

Re: [Axiom-developer] aldor stream oddities

Franz Lehner <[EMAIL PROTECTED]> writes: > is there a way to get hold of generate$Stream using the aldor compiler? Not easily, because: > I spent quite some time until figuring out that generate is probably > a keyword in aldor yes it is. I wrote the following hack to be able to coerce Aldor

[Axiom-developer] aldor stream oddities

Hello, is there a way to get hold of generate$Stream using the aldor compiler? I spent quite some time until figuring out that generate is probably a keyword in aldor (I could not check as the aldor site seems to be down) and this causes strange error messages. The following two snippets do not w

[Axiom-developer] Re: [JenksNotes] (new) Notes of Dick Jenks

Why did you write to axiom-mail? On 08/09/2007 10:58 AM, Martin Rubey wrote: Dear Ralf, thanks for putting this online. However, one general thing: please avoid usage of \begin{verbatim} long text \end{verbatim} since this causes the long text to be saved and downloaded as an image,