Re: Trying to resolve "Internal Compiler Error" Conflict
- From: "Jacky Luk" <jl@xxxxxxxxxx>
- Date: Tue, 10 May 2005 19:49:41 +0800
There is more to say that the conflict might come from the boost C++ library
I'm currently using....
"Jacky Luk" <jl@xxxxxxxxxx> ¼¶¼g©ó¶l¥ó·s»D:%23wEq59UVFHA.1404@xxxxxxxxxxxxxxxxxxxxxxx
> Hi Frank,
> You may only repro that error with VC++ 6.0
> Thanks
> Jack
>
> "Frank Hickman [MVP]" <fhickman_NOSP@xxxxxxxxxxxxxxx> ¼¶¼g©ó¶l¥ó·s»D:O2Y$1PDVFHA.1152@xxxxxxxxxxxxxxxxxxxxxxx
>> "Jacky Luk" <jl@xxxxxxxxxx> wrote in message
>> news:uurRHy6UFHA.2168@xxxxxxxxxxxxxxxxxxxxxxx
>>> Hi,
>>> I have eventually found out the reason why some "Internal Compiler
>>> errors" occurred in the program I've downloaded from the public domain,
>>> was that the programmer had used the "Friend" operators after "using
>>> namespace std", so collapsed during compilation. I commented out that
>>> part but I couldn't pin down the other errors that were caused by
>>> "foreach(...)" and the "string" identifiers all over the places. Do I
>>> definitely have to substitute all "strings" identifiers by "char *" or
>>> that can be resolved somehow or something that can be used in lieu of
>>> the "std" namespace that leads to a successful compilation?
>>> Thanks
>>> Jack
>>
>> The "using namespace std" statement makes it possible to use objects like
>> string str; instead of std::string str; You can remove the statement and
>> replace all the occurances of string with std::string and it will still
>> work properly. Is there some reason why declaring a "friend" to an
>> object and "using namespace std" are not working properly for you? I
>> have used these together without any problems.
>>
>> --
>> ============
>> Frank Hickman
>> Microsoft MVP
>> NobleSoft, Inc.
>> ============
>> Replace the _nosp@m_ with @ to reply.
>>
>>
>
>
.
- References:
- Trying to resolve "Internal Compiler Error" Conflict
- From: Jacky Luk
- Re: Trying to resolve "Internal Compiler Error" Conflict
- From: Frank Hickman [MVP]
- Re: Trying to resolve "Internal Compiler Error" Conflict
- From: Jacky Luk
- Trying to resolve "Internal Compiler Error" Conflict
- Prev by Date: Re: Platform dependent problems
- Next by Date: Re: Platform dependent problems
- Previous by thread: Re: Trying to resolve "Internal Compiler Error" Conflict
- Next by thread: stack around the variable corrupted
- Index(es):
Relevant Pages
|
