Re: C# vs. C++
In article news:<#GZ4sLT2I HA.5472@TK2MSFT NGP06.phx.gbl>, Andre
Kaufmann wrote:
No worries. I got there in the end <smile>
I once confused someone by using [ and ] to represent the limits of
the search box (e.g. search for ["ld"]) ... you can't win!
>
I don't know for sure - I only know that Romans have written them
differently. I assume that all other languages use the same digits
- if I'm not totally wrong.
I don't think you quite understand ...
The Romans used an entirely different system for writing numeric
quantities anyway. In Arabic, numbers are written in base 10 using 10
different digit symbols, but they use different symbols from ours
(and, just to be confusing, their symbol for '5', looks a bit like our
'0').
See Unicode code points U+0660 to U+0669.
But, yes, I can imagine locales (or a locales-like system) supporting
conversion to and from Roman numeral representations too (though as
the Romans had no representation for zero it might be tricky). I can
never remember just what locales do and don't support, beyond the
everyday stuff.
Does that double-negative mean you DO think it IS worth the time? I'm
guessing not, but I can't be sure.
That 2 man years figure that gets bandied about comes, I think, from
Daveed's account of the time it took him. He's a seriously smart guy
so it might take other implementors a little longer ... BUT that time,
AIUI, includes the time taken to implement two-phase lookup which he
found was needed to support export. I think two-phase lookup is going
to have to be done anyway ... so the 2-man-year figure is misleading.
It would be better to do BOTH. Modules don't solve all the same
problems as export ... and export is in the standard TODAY -- all it
needs is acceptance and implementation -- we could have it next year
if there was a will. Modules won't be in any sort of standard before
2012 at the earliest.
Cheers,
Daniel.
In article news:<#GZ4sLT2I HA.5472@TK2MSFT NGP06.phx.gbl>, Andre
Kaufmann wrote:
Sorry, my fault - single quotes have been misleading.
I once confused someone by using [ and ] to represent the limits of
the search box (e.g. search for ["ld"]) ... you can't win!
I'm not sure whether localization covers things like
using different chars (Arabic?) for digits ...?
using different chars (Arabic?) for digits ...?
I don't know for sure - I only know that Romans have written them
differently. I assume that all other languages use the same digits
- if I'm not totally wrong.
The Romans used an entirely different system for writing numeric
quantities anyway. In Arabic, numbers are written in base 10 using 10
different digit symbols, but they use different symbols from ours
(and, just to be confusing, their symbol for '5', looks a bit like our
'0').
See Unicode code points U+0660 to U+0669.
But, yes, I can imagine locales (or a locales-like system) supporting
conversion to and from Roman numeral representations too (though as
the Romans had no representation for zero it might be tricky). I can
never remember just what locales do and don't support, beyond the
everyday stuff.
I too don't think export isn't worth the time (2 man years of
coding).
coding).
guessing not, but I can't be sure.
That 2 man years figure that gets bandied about comes, I think, from
Daveed's account of the time it took him. He's a seriously smart guy
so it might take other implementors a little longer ... BUT that time,
AIUI, includes the time taken to implement two-phase lookup which he
found was needed to support export. I think two-phase lookup is going
to have to be done anyway ... so the 2-man-year figure is misleading.
It would be better to put the time into modules instead.
problems as export ... and export is in the standard TODAY -- all it
needs is acceptance and implementation -- we could have it next year
if there was a will. Modules won't be in any sort of standard before
2012 at the earliest.
Cheers,
Daniel.
Comment