From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,27af4b26a20589ec X-Google-Attributes: gid103376,public From: dennison@telepath.com Subject: Re: with'ing a "foreign" package or subsystem Date: 1999/03/01 Message-ID: <7bea8c$iao$1@nnrp1.dejanews.com>#1/1 X-Deja-AN: 449960496 References: <7bcp7l$1qr@drn.newsguy.com> X-Http-Proxy: 1.0 x1.dejanews.com:80 (Squid/1.1.22) for client 204.48.27.130 Organization: Deja News - The Leader in Internet Discussion X-Article-Creation-Date: Mon Mar 01 15:03:48 1999 GMT Newsgroups: comp.lang.ada X-Http-User-Agent: Mozilla/4.5 [en] (WinNT; I) Date: 1999-03-01T00:00:00+00:00 List-Id: In article <7bcp7l$1qr@drn.newsguy.com>, nabbasi@pacbell.net.NOSPAM wrote: > If I am writing a package now, what can I do to make sure its name in unique? Well, communicating with the other developers on your program would be a good start. :-) On STGT, where we had over a hundred developers, each CSCI (subsystem) in the system had its own designator which had to go on the front of the package name. That reduced the problem to simply communicating with the other developers in your CSCI. This particular case is a bit worse than that, though. Aside from the naming problem, it seems the packages were created to serve the same purpose. Having a subsystem devoted to reusable and reused code helps a lot with this type of problem. It is quite likely that both groups would have realized that "Stack" is something that belongs in the reusable subsystem. Not only would that have prevented the namespace clash, but it also would have prevented the customer from paying to have essentially the same package developed twice! > Actually this can be really a problem, becuase If I build > program, depending on which package of that name it finds 'first', in > its search path, it will use. So by changing the -I order for gnatmake, > one could end up using the other package than the first without > knowing it. (offcourse the change of having 2 packages with same name and > exactly same interface is low, but it can happen). I haven't tried this error with Gnat, but with other compilers this situation got clearly flagged as an error ("can't have two units w/ same name in same compilation", or somesuch). T.E.D. -----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own