Design Decision? Code, Clone or Translate

[Uwe Bonnes]

Hallo,

as stated by some bug entries, the msvcrt implementation of strtod()
understands 'd' and 'D' in addition to 'e' and 'E'. I have stumbled apon
places, where this is needed. The gnu implementation
doesn't understand 'd' and 'D', so we need out own implemenation in
msvcrt. I see three possibilities. Which is best suited?
- Code it ourself
- Clone the implemention from glibc or another open source libc with
suitable license and make this cloned code understand d/D
- Or clone the string, substitute d/D for e/E and call standard libc

Bye

[Peter Beutner]

Uwe Bonnes schrieb:
> Hallo,
>
> as stated by some bug entries, the msvcrt implementation of strtod()
> understands 'd' and 'D' in addition to 'e' and 'E'. I have stumbled apon
> places, where this is needed. The gnu implementation
> doesn't understand 'd' and 'D', so we need out own implemenation in
> msvcrt. I see three possibilities. Which is best suited?
> - Code it ourself
> - Clone the implemention from glibc or another open source libc with
>
> suitable license and make this cloned code understand d/D
> - Or clone the string, substitute d/D for e/E and call standard libc

I would take the last one. Imo it's not worth to duplicate a full-blown parser.

and just substituting is by far the easiest possibility ;)