Date: Fri, 28 Aug 1998 18:39:51 +0300
From: Alexander Bokovoy <bokovoy AT bspu DOT unibel DOT by>
Reply-To: Alexander Bokovoy <bokovoy AT bspu DOT unibel DOT by>
Organization: BSPU named after Maxim Tank
Message-ID: <17777.980828@bspu.unibel.by>
To: Endlisnis <s257m AT unb DOT ca>
CC: djgpp AT delorie DOT com
Subject: Re[2]: Namespaces
References: <35E6BEAB DOT 564DDB62 AT unb DOT ca>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk

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.

Regards,
Alexander Bokovoy, <bokovoy AT bspu DOT unibel DOT by>
--=== The Soft Age coming soon ===--