Re: Endian-ness of "PkgInfo" file
Re: Endian-ness of "PkgInfo" file
- Subject: Re: Endian-ness of "PkgInfo" file
- From: Camillo Lugaresi <email@hidden>
- Date: Sun, 15 Jan 2006 11:35:36 +0100
On 14/gen/06, at 13:32, Dirk Stegemann wrote:
We have an Faceless Background Application with a registered
Creator (TJBR), so the PkgInfo file reads APPLTJBR.
Since a long time, we successfully communicate to this application
by sending AppleEvents which were created using the AECreateDesc()
API, something like this:
-----snip-----
#define kFBASignature "TJBR"
AEAddressDesc gFBAAddress;
OSErr myErr = AECreateDesc (
typeApplSignature,
(Ptr)&kFBASignature,
sizeof(long),
&gFBAAddress);
-----snip-----
On the Developer Transition System, the FBA doesn't recognise the
events until we either change its PkgInfo file to APPLRBJT, or
change the kFBASignature macro to "RBJT".
Is this expected behaviour, or should I file a bug report?
Remember that AppleEvents are an inter-application protocol that can
work across networks. Also, you can now have clients with different
endianness on the same machine (PPC apps running on an Intel Mac with
Rosetta).
Thus is makes perfect sense to me to define the fourcharcodes used by
AE in network byte order, instead of host byte order. I'm actually
surprised that the 10.4u SDK does not define the various constants
using macros (unless align=mac68k also takes care of endianness...
does it?).
Camillo
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden