On 8 Feb 2009, at 11:42, David Chisnall wrote:
On 8 Feb 2009, at 06:47, Richard Frith-Macdonald wrote:
Actually, I take it back ... maybe we can recover from an uncaught
exception.
Problem is ... if we are using native exceptions ... by the time
the uncaught handler is called we have
Am Sonntag, den 22.02.2009, 09:55 + schrieb Richard Frith-Macdonald:
Obviously that breaks binary compatibility on 64bit systesm, but
perhaps less obviously it also breaks source code compatibility in
quite a few places (wherever the API changes from passing a pointer to
a 32bit
On 22 Feb 2009, at 09:55, Richard Frith-Macdonald wrote:
Obviously that breaks binary compatibility on 64bit systesm, but
perhaps less obviously it also breaks source code compatibility in
quite a few places (wherever the API changes from passing a pointer
to a 32bit integer to now be
On 22 Feb 2009, at 12:09, David Ayers wrote:
Am Sonntag, den 22.02.2009, 09:55 + schrieb Richard Frith-
Macdonald:
Obviously that breaks binary compatibility on 64bit systesm, but
perhaps less obviously it also breaks source code compatibility in
quite a few places (wherever the API
On 22 Feb 2009, at 12:42, David Chisnall wrote:
It sounds like a good thing to have the option of resuming, even
though it's generally not advisable.
Do you have a patch for gcc/libobjc which would allow that?
It won't require patching gcc, just libobjc. I don't have a patch
currently,
On 22 Feb 2009, at 12:50, David Chisnall wrote:
On 22 Feb 2009, at 09:55, Richard Frith-Macdonald wrote:
Obviously that breaks binary compatibility on 64bit systesm, but
perhaps less obviously it also breaks source code compatibility in
quite a few places (wherever the API changes from
Am Sonntag, den 22.02.2009, 12:50 + schrieb Richard Frith-Macdonald:
But it seems that we are currently very strict in what we expect. And
we have a bug... NSInteger is typedef'ed to gsaddr (which is typed def
to gsuaddr) instead of gssaddr!
Not in my (as yet uncommitted) code.
On Feb 22, 2009, at 13:50, David Chisnall wrote:
I suspect the bigger problem will be the CGFloat type, which is now
used all over Cocoa. I really don't understand the reason for this
change. It's float on 32-bit and 64-bit on 64-bit platforms, which
almost sounds sensible until you
