jln@portia.Stanford.EDU (Jared Nedzel) (02/20/91)
I've got some questions about using CLOS and packages. I want to divide
my code into several packages, exporting methods and classes as needed.
Here's my questions:
1) do I put the class names in the export list? This seems to
export the class, but not the accessors. (Do they also
need to be exported?)
2) What do you do about methods with the same name that may be
in different files? This seems to cause name conflicts.
Please send e-mail. I'll repost the responses if there's interest.
Thanks.
--
Jared L. Nedzel
---------------------------------------------------------------------
e-mail: nedzel@cive.stanford.edu
jln@portia.stanford.edujohn@mingus.mitre.org (John D. Burger) (02/22/91)
jln@portia.Stanford.EDU (Jared Nedzel) writes: > I've got some questions about using CLOS and packages. I want to > divide my code into several packages, exporting methods and classes > as needed. > 1) do I put the class names in the export list? This seems to > export the class, but not the accessors. (Do they also > need to be exported?) It's important to understand that EXPORT and friends operate on SYMBOLS, not classes or accessors or things that we name with symbols. EXPORT doesn't know that the symbol FLINTSTONE names a class, and that one wants the symbols FLINTSTONE-NAME and FLINTSTONE-AGE, which name accessors, exported as well. In particular, one might NOT want such behavior, in order, for example, to keep internal accessors out of the interface to a module. -- John Burger john@mitre.org "You ever think about .signature files? I mean, do we really need them?" - alt.andy.rooney