[haiku-development] Re: Fixing get_cpu_model_string(), Ticket 3541

  • From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Sun, 21 Jun 2009 11:45:36 +0200 CEST

Christian Packmann <Christian.Packmann@xxxxxx> wrote:
> Axel Dörfler - 2009-06-20 17:40 :
> > Strings are usually the last thing you want to mess with in an
> > (suggested) API like this.
> Not as a means of feature detection; good old bitfields are the
> optimum
> solution there. But at least for my own CPUID API it makes sense to
> include the ability to generate human-readable strings, as one of the
> main
> drives for development is use in my benchmarks and displaying the
> info to
> the user. And exporting the features in the "standard" Linux procfs
> format
> may make sense as well for interoperability purposes like the BOINC
> client.

For this purpose, yes.

> I don't think that this string generation should be part of a OS API,
> at
> least not in the kernel. OTOH, if the OS has the code to generate
> these
> strings anyway (sysinfo), then it may make sense to move the routines
> to a
> library and make them available for other programs which may want to
> use
> this information to display it another form (GUI instead of CLI).

I don't see a reason why. This is something very few apps will ever
need, so having the source available in a shared place would be more
than sufficient.

Bye,
   Axel.

Other related posts:

  1. Home
  2. haiku-development
  3. Archive
  4. 06-2009