Re: Order of cluster searching with ace file (recent snapshot)
Damian DobroczyĆski <[email protected]> Wed, 13 Dec 2006 18:47:00 +0100
| Newsgroups | gmane.comp.lang.eiffel.smalleiffel |
|---|---|
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Cyril ADRIAN napisaĆ(a): > (still playing the devil's advocate...) > > On 12/13/06, Colnet Dominique <[email protected]> wrote: >> For this kind of situation, I would recommend to change at least one >> name. If the concepts are the same, may be we could use only one >> class by merging the two initial classes. If concepts are different, >> two new long name are better. > > Yes, but, what if the libraries are third-parties? After all that's > the aim of libraries: reuse... Do you need to manually rename every > class? > > Or do we need to stick to our "poor man's namespace" class names? > >> Afterall, there is no multiple namespaces in Smalltalk and they >> are building very complex applications. > > Sure. How do they do that? Just curious. > This is an excerpt from comp.lang.eiffel where i asked this kind of question: [http://groups.google.com/group/comp.lang.eiffel/browse_frm/thread/6e8a36b854049a70/fa4ed2592f8e139a?lnk=gst&q=qoocku&rnum=1#fa4ed2592f8e139a] """ qoocku wrote: > I wonder if any of current Lace dialect can assemble classes with the > same name but coming from different clusters (let's assume that class A > from cluster C1 is used by class X and class A from cluster C2 is used > by class Y). Is it possible? cluster: "cluster_path" adapt other_cluster: rename X as XX; another_cluster: rename X as XXX; a_third_cluster: ignore end This renames classes with the same name in different clusters so that the original cluster can refer to them both with different names, - -- Peter Horan """ This is the case of ISE Eiffel LACE dialect. D. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFgDyUWPXp0gyuOusRAt34AKDnODPAwLcMtnzm7X8F8jEt++opvgCg7tqa pjdMwT0PCxjo4A1a5ocVsqY= =P7hw -----END PGP SIGNATURE-----