Re: [AD] CPU info changes

[Bob <ohannessian@xxxxxxxxxx>]

Henrik Stokseth wrote:

> Bob <ohannessian@xxxxxxxxxx> wrote:
>
>
> > > so what about a compromise? from the allegro docs i'd say the following
> info
>
> > > should be available in binary since they are the most likely to be used
> in a
>
> > > game:
> > >
> > > family.
> > > capabilities (int32 bitflags):  fpu, mmx, 3dnow, sse, cpuid
> >
> > Agreed. But family will have to hacked to allow for the Pentium 4
> (currently
>
> > 0xF), the Hammer and the Itanium. The last two of which I can't find any
> > docs about what is exactly returned by CPUID :/
>
> i just got another idea you can have a look at. i'm still thinking about
> ways to ease parsing, while keeping extendablility. :o)
>
> what about providing the info from check_cpu() as a list of name, value
> pairs? where both name and value is a string.


[snip - code]

Although I agree that this is a very nice way of doing things, it seems a 
bit like an overkill for just getting info from the CPU. The 
cpu_capabilities flag is the only one that really matters, and the rest is 
simply for being nice to the user. The idea is good though, and I want to 
see if it can be simplified it a bit.

Martijn's idea seems a bit hackish, hooking over another API for something 
completely (IMO) unrelated. Now, if the rest of Allegro worked that way 
(al_read_config("desktop width", w) for example) then it would make sense.
Then again, maybe for Allegro 5.0...


[snip]



--
- Robert J Ohannessian
"Microsoft code is probably O(n^20)" (my CS prof)
http://pages.infinit.net/voidstar/