jeffshrager/elizagen.org

Reading of 'strings'

Closed this issue · 6 comments

It seems that in BBN-Lisp double quotes (") served as a sort of escape character. For example, I think REALLY"," (from the script) is intended to be read as a single symbol |REALLY,|. That also explains the date header: (QUOTE 08/22/68" 1522:26") is just (QUOTE |08/22/68 1522:26|) and not some bizarre two-argument QUOTE.

Is it possible to hack the Common Lisp reader to accept such things?

I'm sure, but it'd be tricky. You'd have to setup a forward flag or something to capture the next atom to put them together. But at this point I don't think that we need to bother as the I/O is nearly perfect and it's running nearly clean code. Are the punctuation and terminators the only things still sticking out? They are similar to the quote problem, and I similarly wouldn't worry about them. (Oh, there's a couple of easy to fix calls in the main fn that we could easily no-op instead of my commenting them out. I'm not looking at the code, maybe you already did this.)

iTypos bi iPhone

On Nov 26, 2013, at 5:36 AM, pdewacht notifications@github.com wrote:

It seems that in BBN-Lisp double quotes (") served as a sort of escape character. For example, I think REALLY"," (from the script) is intended to be read as a single symbol |REALLY,|. That also explains the date header:
(QUOTE 08/22/68" 1522:26") is just (QUOTE |08/22/68 1522:26|) and not some bizarre two-argument QUOTE.

Is it possible to hack the Common Lisp reader to accept such things?


Reply to this email directly or view it on GitHub.

Yow! Lots of cool work, esp. on the defineq...and I love:

       ;; Also export Symbols named for CL symbols                                                                                                               
       ;; Exports include e.g. BBN-LISP:CONS, and CL:DEFUN                                                                                                       
       ;; but not CL:CONS.                                                                                                                                       
       . #.(loop for s being each external-symbol of :cl
                 collect (symbol-name s))))

!!

I don't get what the sds940-char-code is doing for you. It doesn't appear to be used anywhere (and it's a built in, at least in ccl)???

Jeff: sds940-char-code isn't used at the moment. I just spent some time trying to figure out what the numbers in the SETSEPR and SETBRK lines meant (they obviously couldn't be plain ASCII), and I wanted to document the result somewhere.

Are you sure it's a built-in on ccl? that would be very weird.

m-n commented

I think I learned the trick of exporting CL from PJB:) He uses it in his portable stepper.

Sorry; I meant NOT built in!

----- Original Message -----

Jeff: sds940-char-code isn't used at the moment. I just spent some time
trying to figure out what the numbers in the SETSEPR and SETBRK lines meant
(they obviously couldn't be plain ASCII), and I wanted to document the
result somewhere.

Are you sure it's a built-in on ccl? that would be very weird.


Reply to this email directly or view it on GitHub:
#5 (comment)

Much betterer! :-)

----- Original Message -----

Closed #5.


Reply to this email directly or view it on GitHub:
#5