| Re: [AD] Allegro 4.2.0: The Final Frontier |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On 2005-10-30, Evert Glebbeek <eglebbk@xxxxxxxxxx> wrote:
> > I'll [...] upload the release for internal
> > revision and double checking (Grzegorz' trace patch can go in as far as
> > I'm concerned).
>
> Ok, I put it on my webspace for now in case not everyone knows how to grab
> it from a hidden branch on source forge (I guess only admins can do that
> anyway):
> http://www.eglebbk.dds.nl/allegro-4.2/
> Please all quadruple check and comment on broken things and we'll hopefully
> go gold next week.
I had these changes in my local copy which I haven't committed yet.
I think they're fine.
Peter
Index: docs/src/abi._tx
===================================================================
RCS file: /cvsroot/alleg/allegro/docs/src/abi._tx,v
retrieving revision 1.12
diff -u -r1.12 abi._tx
--- docs/src/abi._tx 27 Aug 2005 01:01:27 -0000 1.12
+++ docs/src/abi._tx 5 Nov 2005 07:51:26 -0000
@@ -43,7 +43,12 @@
<li>MacOS X on PowerPC
</ul>
- XXX: something about backwards vs forwards compatibility
+ We will not be maintaining "forwards compatibility", meaning that
+ programs compiled with a newer release of Allegro may not necessarily
+ run on a target system which has an older release of Allegro installed.
+ You would have to upgrade the Allegro DLL on the target system. While
+ we will try to minimise these kinds of forced upgrades, it should give
+ us more flexibility within the stable series.
Index: docs/src/allegro._tx
===================================================================
RCS file: /cvsroot/alleg/allegro/docs/src/allegro._tx,v
retrieving revision 1.369
diff -u -r1.369 allegro._tx
--- docs/src/allegro._tx 15 Oct 2005 19:30:22 -0000 1.369
+++ docs/src/allegro._tx 5 Nov 2005 07:51:43 -0000
@@ -12377,9 +12377,9 @@
characters that it will accept, and d2 is the text cursor position within
the string.
- Note: dp must point to a buffer at least (d1 + 1) * 6 bytes long because,
+ Note: dp must point to a buffer at least (d1 + 1) * 4 bytes long because,
depending on the encoding format in use, a single character can occupy
- up to 6 bytes and room must be reserved for the terminating null character.
+ up to 4 bytes and room must be reserved for the terminating null character.
@@int @d_list_proc(int msg, DIALOG *d, int c);
@eref exgui