listhelper-moderate
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

help-gplusplus post from address@hidden requires approval


From: help-gplusplus-owner
Subject: help-gplusplus post from address@hidden requires approval
Date: Sun, 08 Jul 2007 20:40:28 -0400

As list administrator, your authorization is requested for the
following mailing list posting:

    List:    address@hidden
    From:    address@hidden
    Subject: Re: 2 pass compiling
    Reason:  Post by non-member to a members-only list

At your convenience, visit:

    http://lists.gnu.org/mailman/admindb/help-gplusplus
        
to approve or deny the request.
--- Begin Message --- Subject: Re: 2 pass compiling Date: 09 Jul 2007 00:11:16 GMT
In article <address@hidden>,
        =?iso-8859-2?q?Seweryn_Habdank-Wojew=F3dzki?= <address@hidden> writes:
> Dears
> 
> I heard some theories, that "it is easy" NOT to force user to properly
> order definitions in classes. And all can be done in two pass

the same would go for declaring variables: the compiler could easily
figure out the variable-type with a second pass. but it doesn't do
so since it would be confusing for the programmer! not all circular
dependencies actually result in meaningful code, so I guess it is
best to avoid all of them anyway. I too experienced this problem:
forward-declaration of a class who's declaration is located within
another class is not allowed in g++, it seems. but is is useful?
-- 
Better send the eMails to netscape.net, as to
evade useless burthening of my provider's /dev/null...

P

--- End Message ---
--- Begin Message --- Subject: confirm a8475c46b4dffab214018acf3e6b2513b42b0694
If you reply to this message, keeping the Subject: header intact,
Mailman will discard the held message.  Do this if the message is
spam.  If you reply to this message and include an Approved: header
with the list password in it, the message will be approved for posting
to the list.  The Approved: header can also appear in the first line
of the body of the reply.

--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]