|
From: | Richard Frith-Macdonald |
Subject: | Re: NSKeyedArchiver/NSKeyedUnarchiver (was Re: GModel decision) |
Date: | Tue, 20 Jan 2004 11:30:13 +0000 |
On 20 Jan 2004, at 02:28, Alexander Malmberg wrote:
Richard Frith-Macdonald wrote:Yep ... especially time consuming as we want to reverse engineer the encoding of the apple classes .. which, as the internal structures of our classes differ from Apples, might mean we are archiving different information to what the current methods do, and reconstructing the information we need from that.Just to clarify: this seems to imply that you think that GNUstep's encoders/decoders should be _directly_ compatible with apple archives, which seems like a Very Bad Idea (as opposed to writing a standalonetranslator, which is a separate project). Is this really what you meant?
Yes. There are people who want MacOS-X compatibility ... and I don't think they should be willfully denied that option. The downside of doing it would be more complex and less efficient codefor reading/writing keyed archives ... but that's a localised issue those
people can deal with without impacting on the rest of the system. Non-keyed archives would be unchanged of course.
[Prev in Thread] | Current Thread | [Next in Thread] |