newlispfanclub.alh.net

Lutz,

I noticed you replaced read-process and write-process with exec.

How about replacing getenv and putenv with env?

Eddie

you mean:

(env str str) = (putenv str str)
(env str) = (getenv str)

and how about ?

(env) = (environ)

not a bad idea, kind of a logical progression, I would introduce env and leave the old getenv/putenv/environ until several releases after? What do other usrers think?

Lutz

sounds logical and consistent

Yes, that's what I mean. Oh yea, I keep thinking to ask but never do

Is println just a pretty print version of write-line? If so, I should be using write-line instead of println for cgi operations. How about a write function like print except no pretty printing?

Eddie

print and println only to pretty-printing when printing lisp espressions. When printing strings no pretty prining is performed. write-line only prints struings and can only take one argument and also can take a file handle.

So there is no reason to prefer write-line over println when printing strings.

Lutz

Thanks Lutz.

I never have used write-line. Does it really have a purpose given println?

Also, I am e-mailing the new version of ecal.cgi with the bell.png image. Overlook the cookie info at the bottom of the applet when setting a reminder. I am going to use that to find out what is up with the time-zone function. I'm on vacation next week, so I probably wont have a time-zone fix for two weeks.

Eddie

write-line can take a filehandle, it belongs to the write-char, write-buffer family.

Lutz