| Re: [AD] CPU info changes |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On Tuesday 23 October 2001 14:44, Laurence Withers wrote:
> > In reply to Bob <ohannessian@xxxxxxxxxx>:
> >I was thinking we get rid of it (less symbols to export).
>
> If nobody strongly disagrees, this is probably a good thing. I wouldn't
> mind, but then I don't use any of these variables.
>
> >We can document how to
> >"get it back" from the cpu_id string. I also don't think it will break too
> > many programs.
>
> Fair enough (at least by me).
having a string to list processor information is ok. but getting rid of
cpu_type, cpu_vedor etc. is something that should be avoided. besides
breaking some programs it also makes it harder and slower to get this info.
parsing a string to fetch this info is just a bad idea IMO.
your original proposal was adding a cpu-info string, and combining various
information in an int, right?
what about putting all info into a cpu struct like this?
struct {
char *desc; /* string with cpu info */
int vendor_id;
int family, model;
int mmx, sse, 3dnow, cpu_id, fpu;
} cpu;
this gets rid of some exports.
and perhaps you should also provide some macros for backwards compatibility?
--
Sincerely Henrik Stokseth.
-----------------------------------------------------------------------
"Our hardware runs better without Windows" - BMW advertisement.
E-mail: hstokset@xxxxxxxxxx Homepage: http://hstokset.n3.net