Custom Query (1030 matches)

If there are multiple strings on one line, only the last is string-colored; the remainder are comment colored.

Ron Garret reports that this seems to fix it, but that undoubtedly interferes with other stuff that r13186 is trying to do.

(defun gui::set-temporary-character-attributes (layout pos start-line end-line)
...
               (let* ((attr (if (= istart 0)
                              (hemlock::lisp-info-begins-quoted parse-info)
                              (if t  ; (< last-end istart)                                                  <==
                                (hi:character-attribute :lisp-syntax
                                                        (hi::line-character line (1- istart)))
                                :comment)))

(/ (complex 1d160 1)) overflows

Answer should be #C(1.0d-160 -9.99988867182683d-321)

Welcome to Clozure Common Lisp Version 1.6-dev-r13678M  (DarwinX8664)!
? (defparameter *s* (make-socket :type :datagram))
*S*
?  (send-to *s* "hey" 3 :remote-host "127.0.0.1" :remote-port 12345)
> Error: value "hey" is not of the expected type (OR (ARRAY CHARACTER)
>                                                    (ARRAY (UNSIGNED-BYTE 8))
>                                                    (ARRAY (SIGNED-BYTE 8))).
> While executing: VERIFY-SOCKET-BUFFER, in process listener(1).
> Type :POP to abort, :R for a list of available restarts.
> Type :? for other options.
1 > 

verify-socket-buffer is actually checking for an 8-bit subtag, and with this new-fangled unicode thing, that doesn't include strings.

My first inclination is to say that i/o on datagram sockets is done in octects. This requires the user to use encode-string-to-octects/decode-string-from-octets explicitly.

It might also be work to pay attention to the socket object's external format and encode the string on the user's behalf, but if Gilgamesh wants to send a cuneiform string "foo", then the actual buffer length in octets isn't going to be 3.