Why not a copy protocol

Article View: comp.lang.clos

Article #312

#312

From: Jose E. Hernandez
Date: Sat, 10 Oct 1992 21:41

12 lines
1007 bytes

Does anyone know why CLOS does not provide a copy protocol.  Although it
is true that in some cases the semantics (as well as the implementation)
of what do we mean by making a copy of an instance can be non-trivial, I
would argue that the same is true with changing the class of an
instance.  Nevertheless, CLOS provides a protocol for this, why not for copy...

thank you!

jose'

PS  I am looking for reasons why CLOS doesn't include a copy protocol,
not necessarily for examples on how to implement one.

Technical Details

Message-ID: <138668@lll-winken.LLNL.GOV>

Path: arc1-ca.pugleaf.net!sparky!uunet!dtix!darwin.sura.net!seismo!lll-winken!windrider.llnl.gov!jeh

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!sparky!uunet!dtix!darwin.sura.net!seismo!lll-winken!windrider.llnl.gov!jeh
From: jeh@windrider.llnl.gov (Jose E. Hernandez)
Newsgroups: comp.lang.clos
Subject: Why not a copy protocol
Keywords: clos copy copy-protocol
Message-ID: <138668@lll-winken.LLNL.GOV>
Date: 10 Oct 92 21:41:25 GMT
Sender: usenet@lll-winken.LLNL.GOV
Reply-To: jeh@llnl.gov (Jose E. Hernandez)
Organization: Lawrence Livermore National Laboratory
Lines: 12
Nntp-Posting-Host: windrider.llnl.gov