newlispfanclub.alh.net

Kazimir Majorinc wrote:When you speak about problems with 27, that means that 1/27 doesn't make nice output, right?

Essentially, yes. When you compare the inverse of 27, 27227, 27272, etc. with any of the others that I listed above, it doesn't seem to be inserting either zeros or other digits as the above numbers do.

cormullion wrote: 9 is a bit odd in my view.

You are so right. And it's also a little square.

Recently, I was doing some number crunching that involved 9 and multiples thereof. Just for fun, look at the digits for the INVERSE of each of these numbers. The "special properties" (whatever that might mean) of 9 have been studied and used since ancient times. In the numbers below, they mostly sho...

so, how did you collect this data, manually or use some nl script? What is this symbol E if formula y=2E+.... and what is R^2?? It was long ago when I worked with math..... :-) The correlation coefficient for a simple linear regression like these tells you how much of the variability in the Y-value...

cormullion wrote:"Common Lisp programmer willing to learn newLISP." Should be interesting... :)

Do any such creatures exist in the DC area? Or do any such creatures exist ANYWHERE on the planet?

I'm wondering why FLOOR runs about 2X slower than CEIL.

DrDave

Heheh.. Well actualy "being Lucky at self-destruct" is partly a good function as you can only do it ones, I tried indeed the harakiri but I did not want to involve a 2nd party... PS the above is about a newlisp function..just to make that clear ;-) PPS Harakiri is an individual action where the Sep...

How did you get those results? With that code the second argument is always evaluated, therefore producing this result: (my-or temp nil) = 45 (my-or nil temp) = 45 ----------- first arg second arg should be 1: 1 ----------- first arg second arg should be 2: 2 Ah, my bad. You're right. I didn't look...

Does this work for you? (define-macro (my-or) (let ( temp (eval (args 0)) temp1 (eval (args 1)) ) (if temp temp temp1 ) ) ) results: (my-or temp nil) = 45 (my-or nil temp) = 45 ----------- first arg should be 1: 1 ----------- first arg second arg should be 2: 2

The problem with [cmd][/cmd] tags in the newLISP-GS Java front-end has been fixed. Download a new guiserver.jar from: http://www.newlisp.org/download/development/guiserver.jar and install on Win32 as: $PROGRAMFILES/newlisp/guiserver.jar or install on Mac OS X and other Unix as: /usr/share/newlisp/g...

I am running newLISP 10.0.0 on WIN 32 IPv4 and newLISP-GS 1.24 on Win XP pro SP2 Your code [cmd] (define (foo x y) (+ x y)) [/cmd] runs fine in both a console and in newLISP-GS. According to the error message, it appears that when you run the code from GS, the two trailing right parentheses have som...

Thanks for the nice analysis of Apply.

cormullion wrote: there are a lot of CL-ers looking for an argument, it seems.

@cormullion, was that "looking for an argument" in reference to "check whether someone supplied extra arguments to function", or meant being argumentative?

I think the CL club has totally forgotten about ...

...it is better to first strive for clarity and correctness and to make programs efficient only if really needed.

"Getting Started with Erlang" version 5.6.2

Maybe someone could write a post explaining how modernizing the antiquated... As I recall, they like to remind those that question the CL dogma that they have a "Standard". While standards usually have a positive aspect, it seems to me that the standard bearers are so afraid of breaking any existin...

The other issue is whether a directory or file can end with "/". I've no idea, it could be a Windows-specific thing. More Windows inconsistencies... On XP, navigate to any folder and attempt to rename it with a backslash or front slash on the end. The error message is A filename cannot contain any ...

Why is there this subtle difference in results? (set 'test-dir1 "C:/Program Files/programming") (set 'test-dir2 "C:/Program Files/programming/") (directory? test-dir1) -->true (directory? test-dir2) -->true (file? test-dir1) -->true (file? test-dir2) -->nil The manual states for true? This function ...

cormullion wrote:I see, but wouldn't claim to understand fully yet.

I'm on the same wagon! How about a different concrete example that might clear away a bit more of the fog.

From what I was able to extract form your earlier posts, you did not install newLISP to the default settings. So, perhaps when you were moving things around, not all your paths match where your target files reside. For example, on my installation using the default settings, I have ("NEWLISPDIR" "C:\...

cormullion wrote:Thanks, Kazimir - that works great.

I had always thought ' and quote were interchangeable...

I also thought they were interchnageable. So perhaps one of the gurus will post an explanation of the difference, and maybe how it came about that we have both of them in the language.

Why does letex create a variable that seems to get evaluated? Because letex creates new expression such that x is replaced with its value, and evaluates that new expression. These two are equivalents ( letex = let & ex pand.) (println (letex ((x 3)) (+ x 3))) (println (let((x 3)) (eval (expand '(+ ...

So just to clarify, we can use letex to set a variable to use in the case selections, but we can't put an expression directly in place of the variable. (set 'n 3 'x 24 'y 8) (letex ((m (/ x y))) (println (case n (1 "one") (2 "two") (m "three") (4 "four")))) --> "three"

I think letex is perfect for that. Something like (but I didn't tested it) (letex ((y (string mystring x))) (case str-to-match (y (string "found" x)))) Lutz did few such things really hitting the target. Now that is very interesting! Why does letex create a variable that seems to get evaluated? Thi...

My original gripe was that exp-1 implied that it was evaluated. It would've been better to call it const-1 so that you get: (case exp-switch (const-1 body-1) [(const-2 body-2) ... ]) You see "const" then you know that you cannot put an expression there. I know it seems a petty matter to those alrea...

Let's just say the 2nd argument "did not need to be" evaluated instead of "never" because it could have been evaluated if we wanted to. Just that the results will not be used. I don't think that is correct for newLISP. My understanding is that in the case where the first argument is true, it is imp...