From mint-bounce@lists.fishpool.fi Thu Dec 10 03:30:31 2009 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=0GUwLl16kQsbAjJPDSuBGaU1i5yfg/IBH1TKrsZUQKY=; b=MZakFirInn2PlByIgC26SMrP839nVxEBARrAm4YBQFTRqUERJRAbxVfIJ9LXDVTSqZ AsfyFwXEm18cbBX7lpYMSZGsXfJ1AxMNom+VIO7ZauPuNgmpRbXvZHcVmX3nw9rJ2a1y RvSuUFKtCzB1RgzEHbjfYLthYnINfJJkM7BgM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=OfTkeYkqYLMuwNaWHCFKVNricKXaq3E5iQ/M+7PULgCPoAzDKaDNb5K3AsZ2Vbw5c0 XwKDgB8OJ0CsgthVcEdXT4VOT9U9VP63pUjRCFNBJboNBm/Iw+EsCSzZRG/CvhnH8DLj nRNPfVUEatDBIhkc2XCwJnw4BBcYQHNtaY56k= MIME-Version: 1.0 Date: Thu, 10 Dec 2009 19:28:04 +1100 Message-ID: <11a6f2b10912100028l6bcb4671xafdac483b5caf82c@mail.gmail.com> Subject: [MiNT] XaAES modifications and clarification From: Paul Wratt To: mint Content-Type: text/plain; charset=ISO-8859-1 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: paul.wratt@gmail.com Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: I have a couple of questions: 1) I want to modify this "typedef enum" declaration (XA_RELATIVE in XA_TYPES.H): LT = 0, /* 0000 */ /* Top right */ LB, /* 0001 */ /* Bottom right */ RT, /* 0010 */ /* Top left */ RB, /* 0011 */ /* Bottom left */ CT, /* 0100 */ /* Top centred */ CB, /* 0101 */ /* Bottom Centered */ CR, /* 0110 */ /* Right centered */ CL, /* 0111 */ /* Left centered */ HLT, /* 0000 */ /* Top right */ HLB, /* 0001 */ /* Bottom right */ HRT, /* 0010 */ /* Top left */ HRB, /* 0011 */ /* Bottom left */ HCT, /* 0100 */ /* Top centred */ HCB, /* 0101 */ /* Bottom Centered */ HCR, /* 0110 */ /* Right centered */ HCL, /* 0111 */ /* Left centered */ As you can see this results in easy confusion when reading large volumes of data where this is used (WIN_DRAW.C) can someone confirm "search for and check/replace on comaprisons", or would there be some underlying (function) checking also required I will verify the L vs R reference before commencing any changes, as it may just be the comments that are wrong. 2) in a header file (XA_TYPES.H) there are some of these: struct remember_alloc; // ??? struct remember_alloc { struct remember_alloc *next; void *addr; }; what is happening here, why the double declaration (see: ???) Thats it for the moment.. Paul