Hi Everybody,
I step in here, with my two euro cents worth.
I see a basic design flaw happening here.
That is you do not to be doing consistency checks.
It is possible to find out if something goes wrong during the arching process.
Check the API for NSKeyedArchiver.
Maybe, I am to old school,
On 2/21/13 5:05 AM, Gerriet M. Denkmann wrote:
On 2/20/13 9:10 AM, Gerriet M. Denkmann wrote:
P.S.
I want my own archiver for 2 reasons:
1. NSKeyedArchiver can store only certain strings
I find that very hard to believe.
I find that very easy to proof:
NSArray *a = @[ @$nill, @$null,
On Feb 20, 2013, at 10:38 PM, Gerriet M. Denkmann gerr...@mdenkmann.de
wrote:
Looks like there is an exception, though nothing gets logged in the Xcode
console:
frame #0: 0x7fff88d483c5 libobjc.A.dylib`objc_exception_throw
frame #1: 0x7fff8ade6e7c
On 21 Feb 2013, at 17:08, Kyle Sluder k...@ksluder.com wrote:
On Feb 20, 2013, at 10:38 PM, Gerriet M. Denkmann gerr...@mdenkmann.de
wrote:
Looks like there is an exception, though nothing gets logged in the Xcode
console:
frame #0: 0x7fff88d483c5
On 22 Feb 2013, at 03:00, Markus Spoettl ms_li...@shiftoption.com wrote:
On 2/21/13 5:05 AM, Gerriet M. Denkmann wrote:
On 2/20/13 9:10 AM, Gerriet M. Denkmann wrote:
P.S.
I want my own archiver for 2 reasons:
1. NSKeyedArchiver can store only certain strings
I find that very hard to
On Feb 21, 2013, at 8:34 PM, Gerriet M. Denkmann gerr...@mdenkmann.de wrote:
Well, the opposite of: can store all strings is: can store only certain
strings.
My point is that the number of unstorable strings is greater than zero.
Whether it is 1 or any other number is quite beside the
On Feb 22, 2013, at 12:15 AM, Jens Alfke j...@mooseyard.com wrote:
* I had something like this happen in one particular development build of
iChat once, due to a bug in the Bonjour status-message code. There was some
particular character you could put in your status message, that would
On Feb 22, 2013, at 1:15 AM, Jens Alfke wrote:
On Feb 21, 2013, at 8:34 PM, Gerriet M. Denkmann gerr...@mdenkmann.de wrote:
Well, the opposite of: can store all strings is: can store only certain
strings.
My point is that the number of unstorable strings is greater than zero.
Whether
I am trying to build my own version of NSKeyed(Un)Archiver.
But I do not know how to recognise mutability.
1. use isKindOfClass: [NSMutableString class]
disadvantage: all strings turn out to be mutable
2. use respondsToSelector: @selector(appendString:)
disadvantage: all strings
On 20 Feb, 2013, at 9:10, Gerriet M. Denkmann gerr...@mdenkmann.de wrote:
I am trying to build my own version of NSKeyed(Un)Archiver.
But I do not know how to recognise mutability.
Use classForKeyedArchiver (or one of the other variants) to detect as which
class an object wants to be
On 2/20/13 9:10 AM, Gerriet M. Denkmann wrote:
P.S.
I want my own archiver for 2 reasons:
1. NSKeyedArchiver can store only certain strings
I find that very hard to believe.
Markus
--
__
Markus Spoettl
___
On 21 Feb 2013, at 00:42, Markus Spoettl ms_li...@shiftoption.com wrote:
On 2/20/13 9:10 AM, Gerriet M. Denkmann wrote:
P.S.
I want my own archiver for 2 reasons:
1. NSKeyedArchiver can store only certain strings
I find that very hard to believe.
I find that very easy to proof:
On Feb 20, 2013, at 12:10 AM, Gerriet M. Denkmann gerr...@mdenkmann.de wrote:
But I do not know how to recognise mutability.
1. use isKindOfClass: [NSMutableString class]
disadvantage: all strings turn out to be mutable
This is somewhat of an FAQ. There is no way to do this (without
On Feb 20, 2013, at 8:05 PM, Gerriet M. Denkmann gerr...@mdenkmann.de wrote:
I find that very easy to proof:
Looks like you’re right — it’s the string @“$null” that’s to blame, for some
reason. I would guess that somewhere in the archiver is some fscked-up
unquoting code. I hope you’ve filed
On 21 Feb 2013, at 11:27, Jens Alfke j...@mooseyard.com wrote:
On Feb 20, 2013, at 8:05 PM, Gerriet M. Denkmann gerr...@mdenkmann.de
wrote:
I find that very easy to proof:
Looks like you’re right — it’s the string @“$null” that’s to blame, for some
reason. I would guess that
On 21 Feb 2013, at 11:15, Jens Alfke j...@mooseyard.com wrote:
On Feb 20, 2013, at 12:10 AM, Gerriet M. Denkmann gerr...@mdenkmann.de
wrote:
But I do not know how to recognise mutability.
1. use isKindOfClass: [NSMutableString class]
disadvantage: all strings turn out to be
On Feb 20, 2013, at 8:39 PM, Gerriet M. Denkmann gerr...@mdenkmann.de wrote:
They are using $null to stand for nil. Which does not play nice with NSArrays
(and other containers), which cannot contain nil.
Plus, the object @“$null” is not the same as a nil pointer, so this is bad
whether or
On 21 Feb 2013, at 12:09, Jens Alfke j...@mooseyard.com wrote:
On Feb 20, 2013, at 8:39 PM, Gerriet M. Denkmann gerr...@mdenkmann.de wrote:
They are using $null to stand for nil. Which does not play nice with
NSArrays (and other containers), which cannot contain nil.
Plus, the object
On Feb 20, 2013, at 9:31 PM, Gerriet M. Denkmann gerr...@mdenkmann.de wrote:
But another bug looks rather promising: feed strings with illegal Unicode to
NSArchiver and see what happens.
It’s harder to get such a string into an app, though, since you can’t really
type it.
Did this (by
On 21 Feb 2013, at 12:58, Jens Alfke j...@mooseyard.com wrote:
On Feb 20, 2013, at 9:31 PM, Gerriet M. Denkmann gerr...@mdenkmann.de wrote:
But another bug looks rather promising: feed strings with illegal Unicode to
NSArchiver and see what happens.
It’s harder to get such a string
20 matches
Mail list logo
