- babel-devel@common-lisp.net - mailman3.common-lisp.net

unsubscribe
by Frank 08 Apr '15

08 Apr '15

unsubscribe

1 0

Test
by Stelian Ionescu 08 Apr '15

08 Apr '15

Test -- Stelian Ionescu a.k.a. fe[nl]ix Quidquid latine dictum sit, altum videtur. http://common-lisp.net/project/iolib

2 1

Invitation personnelle pour rejoindre notre panel
by Opiniometrie 08 Apr '15

08 Apr '15

1 0

Votre Convention collective
by Michel Deloncle 08 Apr '15

08 Apr '15

1 0

patch from qres
by Faré 08 Apr '15

08 Apr '15

I have a patch for babel as used by qres. It was originally written by Scott McKay and Dan Weinreb (RIP), to 1- add support for CESU-8 (as infamously used by Oracle). 2- speed up babel (and measure the speed) Plus by me to 3- support XCVB. I've removed some extraneous type declarations from SWM&DLW, where some other macro already declared a type, and also removed some handling for surrogate codes that was already added upstream since. The patch is attached (against HEAD on github). —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Invent a clever saying, and your name shall live forever. — Anonymous

1 0

Introspection
by Frank 08 Apr '15

08 Apr '15

Hello, I would like to determine the (max) number of bytes a character/units in a certain encoding consumes. Unfortunately there does not seem to be an interface exposed for it (or I just don't see it). I'm doing it this way: (defun max-code-units (encoding) (babel::enc-max-units-per-char (babel::get-character-encoding encoding))) (defun code-unit-size (encoding) (ash (babel::enc-code-unit-size (babel::get-character-encoding encoding)) -3)) (defun max-code-size (encoding) (let ((e (babel::get-character-encoding encoding))) (* (babel::enc-max-units-per-char e) (ash (babel::enc-code-unit-size e) -3)))) Is this a good idea to to that way? Please comment. Thanks, Frank

2 1

[babel-devel] BABEL-TESTS on ABCL
by Erik Huelsmann 28 Oct '12

28 Oct '12

Hi Luis, Today we've been working on ABCL being able to compile and load BABEL; actually, it could do that already, but didn't work with BABEL-TESTS. We've committed some fixes which handle reader issues uncovered by the library, but we're now stuck: there's a bit of code commented out on CCL. It seems we're running into the same problems as CCL, due to strictness of interpretation of code points. Could you mark the #-ccl section in tests/tests.lisp as #-(or ccl abcl)? That solves our problem with the #\udcf0 code point. Thanks in advance! Bye, Erik.

2 1

Re: [babel-devel] [asdf-devel] Tool for transcoding lisp source files and adding coding file options.
by Antony 25 Apr '12

25 Apr '12

On 4/24/2012 8:39 PM, Douglas Crosher wrote: > A tool to add the coding file option to lisp source files is now available. This can also be used to transcode all the files to > UTF-8, or to attempt transcoding to ISO-8859-1 or US-ASCII with loss in comments. There is an example for the current Quicklisp > releases with a few required exceptions. This is experimental, particularly the transcoding to ISO-8859-1 or US-ASCII. Please > backup your code before giving this a try! See: > http://www.scieneer.com/files/transcode.lisp Thanks for sharing. Would be nice if someone puts relevant pieces in a library since this has quite a bit of generally (outside of lisp source file encoding conversion) useful stuff. -Antony

1 0

[babel-devel] error downloading babel
by harven＠free.fr 23 Mar '12

23 Mar '12

Hello, I encounter a problem trying to download babel using quicklisp. I am on debian squeeze and I use the last version of sbcl 1.0.55 that I downloaded 5mns ago from the website, together with a fresh install of quicklisp. I can reproduce the error using the version of sbcl 1.0.40 in the debian repositories. The relevant part of the log which is attached to this message seems to be * (ql:quickload "babel") To load "babel": Load 1 ASDF system: babel ; Loading "babel" ; file: /home/harven/.quicklisp/dists/quicklisp/software/babel-20120208-git/src/enc-unicode.lisp ; in: DEFINE-UTF-16 :UTF-16 ; (BABEL-ENCODINGS::DEFINE-UTF-16 :UTF-16) ; ; caught ERROR: ; (during macroexpansion of (DEFINE-UTF-16 :UTF-16)) ; #:~A-CODE-POINT-COUNTER fell through ETYPECASE expression. ; Wanted one of (STRING SIMPLE-STRING). A similar error has been reported on github https://github.com/cl-babel/babel/issues/9 where it was suggested to run the command (alexandria:format-symbol t '#:~a-code-point-counter "UTF16") Here is what I get. * (ql:quickload "alexandria") To load "alexandria": Load 1 ASDF system: alexandria ; Loading "alexandria" ("alexandria") * (alexandria:format-symbol t '#:~a-code-point-counter "UTF16") debugger invoked on a SB-KERNEL:CASE-FAILURE in thread #<THREAD "initial thread" RUNNING {AB2C889}>: #:~A-CODE-POINT-COUNTER fell through ETYPECASE expression. Wanted one of (STRING SIMPLE-STRING). Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL. restarts (invokable by number or by possibly-abbreviated name): 0: [ABORT] Exit debugger, returning to top level. (SB-KERNEL:CASE-FAILURE ETYPECASE #:~A-CODE-POINT-COUNTER (STRING SIMPLE-STRING)) 0] 0 Any help ? Sincerely, -- Harven

2 2

Re: [babel-devel] [cffi-devel] Unit tests failures on different lisps
by Luís Oliveira 06 Jan '12

06 Jan '12

On Wed, Dec 28, 2011 at 9:25 PM, Anton Vodonosov <avodonosov(a)yandex.ru> wrote: > I am running tests of some most often downloaded CL libraries, including CFFI. > > So far CFFI was only tested on Linux. It has Linux, has different number > (of expected and unexpected) failures on different Lisps. Thanks, this is rather helpful since these days I don't convenient access to all the Lisps/platforms supported by CFFI. Those failures are mostly harmless, although the BFF ones are probably implementation-specific bugs. Is there a way to take advantage of your buildfarm such that I can test CFFI versions before doing a release or before even pushing to the main repository? Cheers, -- Luís Oliveira http://r42.eu/~luis/

2 3