newlispfanclub.alh.net

Of course, in an interactive session *LOAD-PATHNAME* is meaningless.

By the way, clisp has a built-in 'directory-namestring', which is essentially 'dirname', I was asking for in newLISP:

(defconstant *script-dir* (directory-namestring *LOAD-PATHNAME*))

(load (concatenate 'string *script-dir* "../lib/common.lsp"))

There you go.

(load "./lib/common.lsp") will load from the current directory's lib subdirectory. Current directory is variable. But the script should be able to figure out where it is located in the filesystem, and without 'dirname', it's impossible to do. Where do you want common.lsp to be? Anywhere, at a <i>fi...

Thank you. That brings us back to my point #2 above.

What's wrong with Lutz advice is that I don't want to write scripts that will work only with my init.lsp.[/quote]

Lutz wrote:Actually you don't need to use backslash on Win32...
Lutz

??? This information does not help. How about the dirname built-in?

So it would take something like this:     (define (dirname path)         (if (= (& (nth 7 (sys-info)) 0x0F) 6)             (if (regex "(.*\\\\).*" path) $1 ".\\")             (if (regex "(.*/).*" path) $1 "./")))     (define *script-dir* (dirname (nth 1 (main-args)))) in the beginning of each script...

Ok, here is a question: If I am writing several scripts, and I want to put reusable definitions into a separate file, for instance: /home/scratchy/bin/a.lsp <-- one script /home/scratchy/bin/b.lsp <-- another script /home/scratchy/lib/common.lsp <-- reusable stuff Obviously, in a.lsp and b.lsp I nee...

Thanks for the replies. Looks like there are at least two ways to do it, which is technically fine. However the extra syntax on the command-line ([cmd]..[/cmd]) is something that I haven't seen in other shells, and is totally weird. Most shells maintain the same syntax in the script as in interactiv...

Looks like you have been pissing in your beer... too :-)

is that what you do on your period?

meaning?

Can anyone please explain, why would I use newLISP in my software (no matter how great it is) if I have to ask for a permission (who knows what it implies) to use it? When I don't know where Lutz is and how long he's going to be around? I'd rather use good old /bin/sh + homegrown cruft for my script...

How come newlisp gives an error when I type or paste a multiline statement into comment prompt? For example: > (if (env BLAH) missing parenthesis : "...(if (env BLAH)\n" Of course, the paren is missing, because I haven't finished typing yet!!! The newlisp's IQ must be nil to give such an error, cons...