General discussion on Common Lisp Open Code Collection

Janne Rinta-Mänty | 25 Jul 2002 02:56

slot-boundp on conditions

Hello,

There are some define-conditions in (at least) port/ext.lisp and
port/net.lisp that use slot-boundp in their :report clauses.
According to CLHS the consequences of this are undefined.  With CMUCL
(18c) this means that it claims that those slots don't exist (even
when they are initialized).  Maybe the slots could have :initform nil
or something?  Or is there some equivalent of slot-boundp for
conditions?

--

-- 
Janne Rinta-Mänty

-------------------------------------------------------
This sf.net email is sponsored by: Jabber - The world's fastest growing 
real-time communications platform! Don't just IM. Build it in! 
http://www.jabber.com/osdn/xim

headers

Sam Steingold | 25 Jul 2002 15:17

Re: slot-boundp on conditions

Hi,

> There are some define-conditions in (at least) port/ext.lisp and
> port/net.lisp that use slot-boundp in their :report clauses.
> According to CLHS the consequences of this are undefined.

where does it say that?

    This option is processed after the new condition type has been
    defined, so use of the slot accessors within the :report function is
    permitted. If this option is not supplied, information about how to
    report this type of condition is inherited from the parent-type.

--

-- 
Sam Steingold (http://www.podval.org/~sds) running RedHat7.3 GNU/Linux
<http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/>
<http://www.mideasttruth.com/> <http://www.palestine-central.com/links.html>
Never underestimate the power of stupid people in large groups.

-------------------------------------------------------
This sf.net email is sponsored by: Jabber - The world's fastest growing 
real-time communications platform! Don't just IM. Build it in! 
http://www.jabber.com/osdn/xim

headers

Marco Antoniotti | 25 Jul 2002 16:47

Re: slot-boundp on conditions


> X-Sent: 25 Jul 2002 13:17:58 GMT
> Cc: clocc-list <at> lists.sourceforge.net
> Reply-To: sds <at> gnu.org
> Mail-Copies-To: never
> From: Sam Steingold <sds <at> gnu.org>
> Sender: clocc-list-admin <at> lists.sourceforge.net
> X-Original-Date: 25 Jul 2002 09:17:56 -0400
> Date: 25 Jul 2002 09:17:56 -0400
> 
> Hi,
> 
> > There are some define-conditions in (at least) port/ext.lisp and
> > port/net.lisp that use slot-boundp in their :report clauses.
> > According to CLHS the consequences of this are undefined.
> 
> where does it say that?
> 
>     This option is processed after the new condition type has been
>     defined, so use of the slot accessors within the :report function is
>     permitted. If this option is not supplied, information about how to
>     report this type of condition is inherited from the parent-type.

I think there is room for interpretation here.

CLOS is not required for conditions. But "accessors definitions" are.
So it is the use of SLOT-BOUNDP that is not necessarily correct.

Cheers

(Continue reading)

headers

Janne Rinta-Mänty | 25 Jul 2002 19:21

Re: slot-boundp on conditions

Marco Antoniotti 2002-07-25T14:47:27Z:
>> > There are some define-conditions in (at least) port/ext.lisp and
>> > port/net.lisp that use slot-boundp in their :report clauses.
>> > According to CLHS the consequences of this are undefined.
>> 
>> where does it say that?

> I think there is room for interpretation here.

> CLOS is not required for conditions. But "accessors definitions" are.
> So it is the use of SLOT-BOUNDP that is not necessarily correct.

Yes, (sorry, I should have put this in my previous message) it's in
the description of slot-boundp: "Note in particular that the behavior
for conditions and structures is not specified."

--

-- 
Janne Rinta-Mänty

-------------------------------------------------------
This sf.net email is sponsored by: Jabber - The world's fastest growing 
real-time communications platform! Don't just IM. Build it in! 
http://www.jabber.com/osdn/xim