Re: [AD] dmc unicode patch |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On 2007-07-14, Matthew Leverton <meffer@xxxxxxxxxx> wrote:
> On 7/14/07, Peter Wang <novalazy@xxxxxxxxxx> wrote:
> >
> > Instead of setting a variable at initialisation and checking that, it
> > should be fine just check the DMC/Windows version at the time the
> > al_find* functions are called, right?
> >
> I'm not really sure what you mean. Basically any place that has
> IS_OLD_WINDOWS needs to check to see if it's Windows 9x or DMC. And it
> should be renamed from IS_OLD_WINDOWS to something to do with unicode
> paths.
>
> The DMC portion is easy ... it just cannot. MSVC, etc needs a run time
> check to see what version is being used. SYSTEM_NONE doesn't set the
> OS variables (nor should it), so the 4.2.1 system is broken in that
> regard. The easiest Windows check is just to see if the highest bit of
> GetVersion() is set. If it is set, then there won't be any Unicode
> support.
>
> It could be a define like:
>
> #define _al_win_supports_unicode() !(GetVersion() & 0x80000000)
>
> and for DMC it is just false.
Can I get a patch to this effect? Then I think I can release 4.2.2
tomorrow, unless you want to resolve the OSX universal binaries first?
Peter