Symbian unprotected Uids

😊) The development UIDs are starting at 0xE0000000. 😊)
As such one will never need 0xAxxxxxxx UIDs as one will never have a running
app to sign. Ain't that fun ?!

"Guillaume" <[email protected]> wrote in message
news:jlH4dNNKGHA.3100@extapps30...
> 1. TUid::iUid is defined as a TInt32
> 2. const TInt KMaxTInt32=0x7fffffff;
> 3. unprotected uids allocated by Symbian start at 0xA0000000
>
> Not very friendly !!!
>
>
>
>

1. TUid::iUid is defined as a TInt32
2. const TInt KMaxTInt32=0x7f f f f f f f;
3. const TInt KMinTInt32=(TInt)0x80000000;

TInt/TInt32 are signed integers (two's complement). So both the development
UID range and the unprotected UID range are valid UIDs.

Regards
Martin

"Lasse" <[email protected]> wrote in message news:kaRc%23MPKGHA.3100@extapps30...
> 😊) The development UIDs are starting at 0xE0000000. 😊)
> As such one will never need 0xAxxxxxxx UIDs as one will never have a
running
> app to sign. Ain't that fun ?!
>
> "Guillaume" <[email protected]> wrote in message
> news:jlH4dNNKGHA.3100@extapps30...[color=green]
> > 1. TUid::iUid is defined as a TInt32
> > 2. const TInt KMaxTInt32=0x7fffffff;
> > 3. unprotected uids allocated by Symbian start at 0xA0000000
> >
> > Not very friendly !!!
> >
> >
> >
> >
>
>[/color]