[capidl] scopes

[Jonathan S. Shapiro]

> On the other hand, there is a second
> possible objective, which is to automatically generate an constructors for
> both individual objects (domains?) *and* for applications comprised of
> collections of objects.

This is not a CapIDL objective. The sole purpose is glue code. Generating
constructors that work across multiple language runtimes to correctly
construct objects is impossibly hard, and would require a substantial
programming language in and of itself.

> On first blush, if constructor generation
> is desired, the CapIDL grammar will have to be augmented with an "uses"
> keyword that can be associated with an interface to indicate the other
> interfaces that will be called from within the interface implementation.

This would be nice, and probably desirable. The CORBA folks specified use of
the C Preprocessor, however, which encourages the use of #include for this
purpose.


Jonathan