By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
446,190 Members | 944 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 446,190 IT Pros & Developers. It's quick & easy.

/GX compiler option

P: n/a
Hi ,
I have faced a strange problem. I have a code something like this...
while(!a)
{
if( condition )
{
continue; // 1
}
try
{
if ( condition )
{
if( some more condition )
{
a = 1;
continue; // 2
}
else
{
continue; // 3
}
}
else
{
}
}// end try
catch(...)
{
} // end catch
}// end while

In this piece of code with the continue keyword used i expect it to go back to the outer while... This happens in all the if statements for e.g. with the continue 1.
But the presence of continue keyword in the try block gave me an INTERNAL COMPILER ERROR . This got solved when i gave a preprocessor option called /Gx. This was prompted to me as a warnig by the compiler which solved this problem.

Now i have not understood why was this an error and how does /Gx option help in that .

Thanks
Param
Jul 19 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
"Param" <se******@yahoo.com> wrote in message news:<bg**********@news.mch.sbs.de>...
Hi ,
I have faced a strange problem. I have a code something like this...
while(!a) ....
In this piece of code with the continue keyword used i expect it to go
back to the outer while... This happens in all the if statements for
e.g. with the continue 1.
But the presence of continue keyword in the try block gave me an
INTERNAL COMPILER ERROR . This got solved when i gave a preprocessor
option called /Gx. This was prompted to me as a warnig by the compiler
which solved this problem.


We can't help you, this group is only about standard C++ and that
doesn't specify compiler options. You don't even say which compiler,
so we can't point you to the right group for that compiler. Google
can tell you that if you tell it what compiler you have.

Regards,
--
Michiel Salters
Jul 19 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.