newlispfanclub.alh.net

Thanks, Lutz. I'll play with those variations.

What is a more idiomatic way to do this? : (set 'tmp-file (open "/tmp/file" "write")) (write tmp-file (join (map markup (parse pretext "\n" 0)) "\n")) (close tmp-file) (setf posttext (join (exec "fmt -68 /tmp/file") "\n")) It feels dirty to use a /tmp/file like that. Ideally I'd like to pipe a strin...

An only slightly more harmonious solution might be to go the other way and expect URL literal command-line arguments to be marked up so as to prevent them being remotely executed by newLISP. Prepending a + is one simple way: newlisp +http://www.google.com/bank.html getting the url then as: (setf url...

cool

just a stab in the dark here, csfreebird, but you said you were on amd64 but then went and installed:
?

I am assuming the error message:
is saying that it expected a 64-bit ELF class...

Thanks for the list of places to cover, Lutz. Adding adhoc constants to individual scripts will lead to an inevitable mess of misspellings. The idea of a company-wide constants module is good -- and such a project would be the beginnings of a globally used Constants.lsp or English.lsp or SomeSuch.ls...

Good to know, Lutz, thanks. So... care to weigh in on the magic-number side? This phenomenon exists in several places throughout the newLISP API. Many functions take an optional integer parameter that is an OR compositie of individual option values. As bare numbers, this makes reading code quite dif...

Thanks for playing along, Cormulion. Your solution is certainly the easiest of the named-symbols implementations. On the down side, it produces fairly verbose symbols. Another question I had about the code: two fours? Is it possible for the state of (last-error) to change between testing for Error:p...

o_O Some magic Lutz code: (error-event (fn () (if (= 4 ((last-error) 0)) (println "ERR:" (last (last-error 4))) (println ((last-error) 1))))) For a while now I have been unconsciously squirming in my seat when reading over code like this. This morning I became aware of that discomfort and cried in ...

I have never done net coding, but I thought that was exactly what the (pack ...), (unpack ...) pair were for - to be able to send binary values encoded as strings to be decoded back into their proper forms at the other end. No?

I'm going to guess here, csfreebird, that you can use the (pack ...) and (unpack ...) functions for this. See the newLISP User Manual for these functions. From a quick look, it would seem you'd use: (pack ">d" your_short) For a signed big-endian short. Heh... and on clicking Submit, it seems that Co...

There is the
analogue too... :-/

This bit me yesterday when I was testing jazper's sqlite3 stuff. I whimped out and created a symlink from /usr/local/lib/libsqlite3.so, but that really was just a kludge.

o_O what am I gonna do with all this popcorn?! Thanks, RickyBoy & Cormullion - it was the case sensitivity issues I was unsure about. I was fairly sure that the NULL was necessary - it seemed so in standalone tests of sqlite3.lsp. I don't think I made any other changes, jazper, apart from the aesthe...

Try: #!/usr/bin/newlisp ;;; to create table, used this -- CREATE TABLE UsrTbl(Id INTEGER PRIMARY KEY, UserName TEXT, UserEmail TEXT) (print "Content-type: text/html\n") (module "cgi.lsp") (module "sqlite3.lsp") (println [text] <br> <form action="UPDTDB2.cgi" method="POST"> <pre> User name:<input typ...

Use the (copy ) function on the string.

This is shown in CodePatterns under Walking A Directory Tree in section 5.

Without seeing your data, I can only guess at the structure. As such, this code will almost certainly fail: (map rest (ref-all '("title" *) x match true)) Hopefully the intent survives though and you're able to find a built-in search function to suit your needs. There are about three hundred of them...

It is the wise man who chooses another direction when he sees he's on the wrong path. Well played, rickyboy. Intellectually, I get why the macro form is not playing nice for us, but I lack the necessary coalface time at the keyboard to properly internalise that lesson. This is an area of my lisp tha...

Ah... a snag I hit in the macro forms, rickyboy, is the resulting order of execution when called on a nested call of itself: (define (get_workspace_trees , x) (let (x '()) (dolist (output (get_active_output_names)) (push (list output (nodes "content" (nodes output (get_tree)))) x)) x)) The code for ...

Wow. That's brilliant, rickyboy! Thanks for taking the time to show and explain those ideas to me. That is exactly what I was looking for (but didn't know what it would look like) when I asked for places to improve my code. I am new to lisp, so knowing when to reach for a macro is still beyond my re...

...does that come with a cape and hat? 'cos if there's a cape and hat, i'm in! ...ok, i'd settle for just the hat...

Thanks, Cormullion. I must have tried a hundred different ways to call (ref...) today with maddening ocassional successes and frustratingly more failures so coyly announced by newLISP simply as: nil I used your code to have another go, and it worked. Here is my new (nodes...) function: (define (node...

I have a deeply nested tree of lists (which came from json (the i3-tag -t get_tree command from the i3 window manager, specifically)). What is the best way in newLISP to drill down into various parts of this structure? I have so far been using code like: ((assoc "nodes" (((assoc "nodes" ((get_tree) ...

I should have thought about copy(). I have to do that all the time in Vim because its map() function is destructive. :-/

Thanks for the reminder, and speed test, Cormullion. Completed this thread nicely, I'd say. :-)

W00t! Learned about replace() today. Yay. :-) Thanks, cormullion. It was interesting to see Michael's speed test. I hadn't thought about how slow map() might be. And what a speed difference! Another thing to note about the two different solutions, though, is that the map() is non-destructive, wherea...