Re: string substitution?
- From: "John Thingstad" <john.thingstad@xxxxxxxxx>
- Date: Thu, 30 Nov 2006 22:09:48 +0100
On Thu, 30 Nov 2006 20:34:48 +0100, André Thieme <address.good.until.2006.dec.22@xxxxxxxxxxx> wrote:
Pascal Bourguignon schrieb:André Thieme <address.good.until.2006.dec.22@xxxxxxxxxxx> writes:
Pascal Bourguignon schrieb:Implementation specific.This is incorrect. #\Newline has no relation with CR or LF.At least on sbcl there seems to be a relation:
(concatenate 'string (string #\Return) (string #\Linefeed)))
But I can say that at least sbcl works this way.
And clisp. Not to forget Allegro. Oh, and cmucl.
But maybe all the other lisps act different in that regard, so probably
you are right, and there mostly is no relation between #\Linefeed and a
All running Unix right?
That is because #\Linefeed is a gives a newline under Unix.
However under Windows it just goes to the next line.
A #\Return is needed to send it to the beginning of line.
(Like on a typewriter)
I come across this a lot having to convert #\Newline to
#\Return #\Newline. By the way a Mac used (does it still use?)
just #\Return. This is probably the reason for the routine.
I should have caught the problem myself. For Unix compatabillity
Emacs typically handles both cases for Windows and Unix.
So LispWorks for Windows handles #\Linefeed as #\Newline.
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
- Prev by Date: Re: SBCL just turned 1.0!
- Next by Date: Re: LISP OS starting point
- Previous by thread: Re: string substitution?
- Next by thread: Re: string substitution?