On Nov 11, 2011, at 12:25 AM, Iain Sandoe wrote:
> FWIW your example doesn't reproduce the problem because it contains no
> objective c exceptions code.
Ah, but it can be seen to contradict what you said. It also found a bug.
> However, OK - I see your point (I also see where the problem came f
On 11 Nov 2011, at 00:30, Mike Stump wrote:
On Nov 10, 2011, at 9:40 AM, Iain Sandoe wrote:
Thanks for catching that --- brainstorm on my part ... the code
under discussion should have been #ifndef OBCPLUS
There is no prohibition against C having exceptions, so, doesn't
matter if you turn
On Nov 10, 2011, at 9:40 AM, Iain Sandoe wrote:
> Thanks for catching that --- brainstorm on my part ... the code under
> discussion should have been #ifndef OBCPLUS
There is no prohibition against C having exceptions, so, doesn't matter if you
turn C++ off, you can still throw through C code, s
Hi Mike,
just want to state my understanding to allow you to comment if I'm
off
On 10 Nov 2011, at 16:12, Mike Stump wrote:
On Nov 10, 2011, at 1:35 AM, Richard Guenther
wrote:
flag_exceptions also triggers middle-end behavior - without it no
statement can possibly throw
Actually,
On Nov 10, 2011, at 1:35 AM, Richard Guenther wrote:
> flag_exceptions also triggers middle-end behavior - without it no
> statement can possibly throw
Actually, one version of exception handling for objective c++ doesn't require
flag_exceptions... One can indeed @throw without it, they just ca
On Wed, 9 Nov 2011, Mike Stump wrote:
> On Nov 9, 2011, at 10:12 AM, Iain Sandoe wrote:
> > This puts "flag_next_runtime" into the global options structure
>
> > I needed to deal with '-fobjc-sjlj-exceptions' and elected to remove it -
> > - this is because there is only one valid exception mod
On Nov 9, 2011, at 10:12 AM, Iain Sandoe wrote:
> This puts "flag_next_runtime" into the global options structure
> I needed to deal with '-fobjc-sjlj-exceptions' and elected to remove it -
> - this is because there is only one valid exception model for each
> permutation of runtime and ABI - t
On Wed, 9 Nov 2011, Iain Sandoe wrote:
> I am probably missing something
> - but there doesn't seem to be a ready way to set the Init() value of a flag
> depending on the target
The way that is done is to use an expression inside Init() that uses a
target macro (it needs to be a macro, not a hoo
