RE: About the declare-flow-object-class

Subject: RE: About the declare-flow-object-class
From: Avi Kivity <Avi@xxxxxxxxxxxxx>
Date: Tue, 6 Jul 1999 09:43:54 +0300
On Sunday, July 04, 1999 15:26, Didier PH Martin
[SMTP:martind@xxxxxxxxxxxxx] wrote:
> 
> Specs extract:
> [178] application-flow-object-class-declaration = (declare-flow-
> object-class
> identifier string)
> This declares identifier to be a flow-object-class-name for a class
> with a
> public identifier
> specified by string.
> 
> It is said that it is an application specific flow object but
> nothing is
> said about how this is created or where this is stored.
> 
> Question: Does somebody has an idea why a string or public
> identifier is
> needed?

1. A flow object name (symbol) cannot be guaranteed to be unique, but a
public identifier ought to be.
2. A public identifer allows specification of additional information via an
external mechanism (for example, the name of the library implementing the
flow object)
3. Consistency - anything external or extensible is defined via a public
identifier (color spaces, for example)

"Any computer science problem can be solved with an additional level of
indirection"

---
"The only words which have meaning are the last ones spoken"



 DSSSList info and archive:  http://www.mulberrytech.com/dsssl/dssslist


Current Thread