Re: with'ing a "foreign" package or subsystem

[dennison@telepath.com]

In article <7beg6a$2o4d@news1.newsguy.com>,
  Samuel Mize <smize@imagin.net> wrote:
> Matthew Heaney <matthew_heaney@acm.org> wrote:
> > Can both packages coexist in the same application?  Is there a way to
> > give a package a "virtual" subsystem, to prevent name-space conflicts
> > like this?  Something like:
> >
> > package ACME.Stacks renames <ACME company's "Stacks">;
>
> I assume you would also change the name of ACME's Stacks, so your
> Stacks and ACME's Stacks would no longer collide.
>
> Having done that, you may as well just use the altered name.  Won't you
> have to rework the code that uses them just as much either way?
>
> Did I miss something here?  I'm not trying to give a smart-ass reply,
> I honestly don't see where you're heading.

I think what he's getting at (correct me if I'm wrong here Matt), is that he
wants to be able to "reveal" the first declaration of an object by renaming
the second declaration off of it.

While I think lots of use-philes would like that capability too,....YUK!

> I'd say parent packages defining independent name-spaces is the
> intended mechanism for preventing conflicts.  To resolve them after
> they occur, I think you just have to bite the bullet and rename one
> of them.

Yeah. You're looking for a language solution to what was really a management
problem. Chalk this one up to experience, fix it, and move on.


T.E.D.

-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/       Search, Read, Discuss, or Start Your Own