June 2008 - clpython-devel@common-lisp.net

[clpython-devel] Re: CLPython on SBCL
by Jason Nielsen 07 Jul '08

07 Jul '08

I can confirm that compilation fails using SBCL 1.0.16 on a Ubuntu 7.10 system with a: "has no suitable method for STREAM-ELEMENT-TYPE, and so has fallen through to this method...." error that crashes the whole session. You can reproduce this behaviour with the following: (defclass foo (standard-class) ()) (defclass bar () () (:metaclass foo)) Cheers, Jason

3 23

[clpython-devel] New errors in recent CVS
by Jason Nielsen 14 Jun '08

14 Jun '08

Hello, I just pulled the recent changes from cvs and get the following warning when building: The constant CLPYTHON.PARSER::+ALL-VALUES-NAMES+ is being redefined (from (CLPYTHON.PARSER:+NORMAL-VALUE+ CLPYTHON.PARSER:+AUGASSIGN-VALUE+ CLPYTHON.PARSER:+NO-VALUE+) to (CLPYTHON.PARSER:+NORMAL-VALUE+ CLPYTHON.PARSER:+AUGASSIGN-VALUE+ CLPYTHON.PARSER:+NO-VALUE+)) which I accept and the build finishes. When I run the test suite I get the following: ********************************** End CLPython test Errors detected in this test: 104 UNEXPECTED: 100 Successes this test:609 ; ; compilation unit finished ; caught 114 fatal ERROR conditions ; caught 4 ERROR conditions ; caught 3 WARNING conditions ; caught 22 STYLE-WARNING conditions ; printed 26 notes NIL There are a whole bunch of error messages when running the tests of the form: Reason: detected an unexpected error of type `#<SB-PCL::CONDITION-CLASS SB-C:COMPILER-ERROR>': which are the likely cause of the 100 extra failures. All of this is on a Ubuntu 7.10 box with sbcl 1.0.17... I built the latest sbcl along with the previous tarball I had and the test suite ran as expected so the problem is in recent updates. By the way I've been following Euro 2008 closely (I'm a huge soccer/football fan which isn't quite as common here in Canada) and the Dutch team are looking awesome! Nothing like kicking the asses of the reigning world champs and runners-up to start off the tournament ;-). Jason

2 2

[clpython-devel] Python just got a bit less dynamic
by Willem Broekema 13 Jun '08

13 Jun '08

Guido just limited the dynamicness of Python in a very sensible way, by declaring that the attributes of objects can only be regular strings. For users this does not change much, but for implementors this has significant benefits, so I like this limitation a lot. The implementation of attributes in CLPython and other implementations can now be cleaned up and made more efficient by removing hairy corner cases. CLPython can now always represent attributes by Lisp symbols. Also as a result, the five known failures in the CLPython test suite, which tested some hairy corner cases, are now defined to not be failures at all. The decisions: - Using non-string keys is undefined behavior; non-empty strings that are not valid as identifier according to the grammar are allowed: http://mail.python.org/pipermail/python-dev/2008-June/080309.html - String subclasses may be normalized to regular strings: http://mail.python.org/pipermail/python-dev/2008-June/080312.html - The restriction applies to both class dicts and instance dicts: http://mail.python.org/pipermail/python-dev/2008-June/080313.html - Frameworks currently using non-string attributes should change their behavior; http://mail.python.org/pipermail/python-dev/2008-June/080319.html - Willem

1 0