Aici e o problema de tip "fa-o cum trebuie". Daca lucrezi cu
<iostream> (asha cum, de acord, e corect) shi nu cu <iostream.h>,
atunci ar fi bine sa impui aceeashi rigoare shi in ceea ce se numeshte
accesarea namespace-ului.
Daca incepi o chestie riguros, nu cred ca poti gasi o scuza in lipsa
de rigoare din alte partzi.
O intrebare (nu am gcc 3.2 aici). Daca incluzi <iostream.h> merge
fara using namespace?
On Thursday 14 November 2002 10:08, Daniel Pavel wrote:
> Dorin Lazar wrote:
> > Nu este nevoie, decat daca apare namespace polution. el zicea ceva
> > de cout? care e c++ toata ziua? Shi ma indoiesc ca suprascria
> > cout-ul... cel putsin asha a dat de intseles?
>
> [pwr@machine]/usr/include/c++/3.2$ cat iostream
> // Standard iostream objects -*- C++ -*-
>
> [GPL snipped]
>
> #ifndef _CPP_IOSTREAM
> #define _CPP_IOSTREAM 1
>
> #pragma GCC system_header
>
> #include <bits/c++config.h>
> #include <ostream>
> #include <istream>
>
> namespace std // <=== relevant part starts here
> {
> extern istream cin;
> extern ostream cout;
> extern ostream cerr;
> extern ostream clog;
> #ifdef _GLIBCPP_USE_WCHAR_T
> extern wistream wcin;
> extern wostream wcout;
> extern wostream wcerr;
> extern wostream wclog;
> #endif
>
> // For construction of filebuffers for cout, cin, cerr, clog et.
> al. static ios_base::Init __ioinit;
> } // namespace std
>
> #endif
> =======[ end of file ]=======
--
Dorin Lazar, programmer
Registered Linux user #162515
---
Pentru dezabonare, trimiteti mail la
[EMAIL PROTECTED] cu subiectul 'unsubscribe rlug'.
REGULI, arhive si alte informatii: http://www.lug.ro/mlist/
