Message-Id: <199808281904.VAA51336@ieva06.lanet.lv>
From: "Andris Pavenis" <pavenis AT lanet DOT lv>
To: Endlisnis <s257m AT unb DOT ca>, Alexander Bokovoy <bokovoy AT bspu DOT unibel DOT by>
Date: Fri, 28 Aug 1998 21:08:34 +0300
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: Re[2]: Namespaces
CC: djgpp AT delorie DOT com
In-reply-to: <17777.980828@bspu.unibel.by>
Precedence: bulk

Date sent:      	Fri, 28 Aug 1998 18:39:51 +0300
Subject:        	Re[2]: Namespaces

> Endlisnis wrote:
> > Myknees wrote:
> >> >What is that? I heard that term now several times and I don't have a =
> >> >clue. :)
> >> It's a new feature in C++ that lets you put all the names in a library in their
> >> own little package, so that by using the libary you don't have to have all of
> >> those names conflicting with names in other libraries.
> >> 
> >> e.g. The standard library functions would be in namespace std.  It looks like
> >> this:
> >> mylibspace::print();
> >> 
> >> ...where mylibspace is a namespace.
> >         Isn't that just a 'class'?
> No. Namespaces should use to avoid variables, functions and types
> conflicts between different libraries. For example, while SWORD
> developments I got conflict between our graphical context, GrContext,
> which is class and GRX's GrContext, which is struct. Unfortunately,
> GCC 2.8.1 doesn't support namespaces well. So, we changed our
> GrContext to GSContext to avoid conflict. It is isn't bad but isn't
> good too.
> 

gcc-2.8.1 says:  sorry, not implemented: namespace

Looks than namespaces works at last partially with latest 
development snapshots of egcs-1.1. I myself am not using them
so I only tested a simple example with DJGPP port of egcs-2.91.54
19980816. Release of egcs-1.1 is expected at end of month so
rather soon (see http://egcs.cygnus.com)

Andris