"Richard Heathfield" <rjh@see.sig.invalid> a écrit dans le message de news:
t_KdnR8gONyx4ZfanZ2dnUVZ8taknZ2d@bt.com...
<snip>
> "Big endian" means that the most significant values come first in the
> underlying representation. A good example is prices in a shop: when we see
> 39.99 on a pair of jeans, we know that it's about 40 currency units, not
> almost a hundred currency units. "Little endian" means that the least
> significant values come first - and I suppose the obvious example would be
> UK date format: day/month/year.

As compared to the big endian notation year.month.day used for example in
Japan,
and the braindead endian mixup month/day/year used in the USA.

Lets refine your currency example: numbers are written in big endian decimal
representation in English, but the same ordering of the digits in Arabic is
indeed little endian. The digits are different and the reading order is
still big endian though. Yet in German, the reading order is different
again: 42 is pronounced zwei und vierzig, big endian writing, little endian
reading (for 2 digits only ;-)

--
Chqrlie.

"Charlie Gordon" <news@chqrlie.org> schrieb im Newsbeitrag
news:47195862$0$24602$426a34cc@news.free.fr...
> "Richard Heathfield" <rjh@see.sig.invalid> a écrit dans le message de
> news: t_KdnR8gONyx4ZfanZ2dnUVZ8taknZ2d@bt.com...
> <snip>
>> "Big endian" means that the most significant values come first in the
>> underlying representation. A good example is prices in a shop: when we
>> see
>> 39.99 on a pair of jeans, we know that it's about 40 currency units, not
>> almost a hundred currency units. "Little endian" means that the least
>> significant values come first - and I suppose the obvious example would
>> be
>> UK date format: day/month/year.
Same format in the rest of Europe, only a different separator:
day.month.year
The UK format is pretty hard to distinguish from the US format

> As compared to the big endian notation year.month.day used for example in
> Japan,
The most sensible IMHO, makes sorting easiest.

> and the braindead endian mixup month/day/year used in the USA.
Indeed

> Lets refine your currency example: numbers are written in big endian
> decimal representation in English, but the same ordering of the digits in
> Arabic is indeed little endian. The digits are different and the reading
> order is still big endian though.
I think I've heard that Arabic uses the same little Endian for 2-digit
number as in Germany.

> Yet in German, the reading order is different again: 42 is pronounced zwei
> und vierzig, big endian writing, little endian reading (for 2 digits only
> ;-)
Actually for the last 2 digits of every number greater then 12.
A broken concept IMHO. I grew up with it and used all my life and still make
mistakes...
But not as broken as the french numbers between 70 and 99 8-) (and
apparently fixed in the french speaking parts of Belgium and Switzerland)

Bye, Jojo

"Joachim Schmitz" <nospam.jojo@schmitz-digital.de> a écrit dans le message
de news: ffcgov$ohv$1@online.de...
>
> "Charlie Gordon" <news@chqrlie.org> schrieb im Newsbeitrag
> news:47195862$0$24602$426a34cc@news.free.fr...
>> "Richard Heathfield" <rjh@see.sig.invalid> a écrit dans le message de
>> news: t_KdnR8gONyx4ZfanZ2dnUVZ8taknZ2d@bt.com...
>> <snip>
>>> "Big endian" means that the most significant values come first in the
>>> underlying representation. A good example is prices in a shop: when we
>>> see
>>> 39.99 on a pair of jeans, we know that it's about 40 currency units, not
>>> almost a hundred currency units. "Little endian" means that the least
>>> significant values come first - and I suppose the obvious example would
>>> be
>>> UK date format: day/month/year.
> Same format in the rest of Europe, only a different separator:
> day.month.year
> The UK format is pretty hard to distinguish from the US format

France uses day/month/year as well.

>> As compared to the big endian notation year.month.day used for example in
>> Japan,
> The most sensible IMHO, makes sorting easiest.

As long as year, month and day are formated with a fixed number of digits
;-)

>> and the braindead endian mixup month/day/year used in the USA.
> Indeed
>
>> Lets refine your currency example: numbers are written in big endian
>> decimal representation in English, but the same ordering of the digits in
>> Arabic is indeed little endian. The digits are different and the reading
>> order is still big endian though.
> I think I've heard that Arabic uses the same little Endian for 2-digit
> number as in Germany.

Yes, I forgot about that! so it is consistently little endian for 2 digit
numbers. (above 11, and except multiples of 10 ;-)

>> Yet in German, the reading order is different again: 42 is pronounced
>> zwei und vierzig, big endian writing, little endian reading (for 2 digits
>> only ;-)
> Actually for the last 2 digits of every number greater then 12.

And for the low digit pairs in every group of three for larger numbers.

> A broken concept IMHO. I grew up with it and used all my life and still
> make mistakes...
> But not as broken as the french numbers between 70 and 99 8-) (and
> apparently fixed in the french speaking parts of Belgium and Switzerland)

Not all numbers between 70 and 99, and not all parts of French speaking
Switzerland and Belgium: 80 to 89 are based on quatre-vingts in Belgium and
all but a few cantons in Switzerland... As usual, French language subtleties
are unfathomable: http://www.langue-fr.net/index/S/septante.htm -
http://fr.wikipedia.org/wiki/80_(nombre)

--
Chqrlie

"Charlie Gordon" <news@chqrlie.org> schrieb im Newsbeitrag
news:4719ed78$0$5073$426a74cc@news.free.fr...
> "Joachim Schmitz" <nospam.jojo@schmitz-digital.de> a écrit dans le message
> de news: ffcgov$ohv$1@online.de...
>>
>> "Charlie Gordon" <news@chqrlie.org> schrieb im Newsbeitrag
>> news:47195862$0$24602$426a34cc@news.free.fr...
>>> "Richard Heathfield" <rjh@see.sig.invalid> a écrit dans le message de
>>> news: t_KdnR8gONyx4ZfanZ2dnUVZ8taknZ2d@bt.com...
>>> <snip>
>>>> "Big endian" means that the most significant values come first in the
>>>> underlying representation. A good example is prices in a shop: when we
>>>> see
>>>> 39.99 on a pair of jeans, we know that it's about 40 currency units,
>>>> not
>>>> almost a hundred currency units. "Little endian" means that the least
>>>> significant values come first - and I suppose the obvious example would
>>>> be
>>>> UK date format: day/month/year.
>> Same format in the rest of Europe, only a different separator:
>> day.month.year
>> The UK format is pretty hard to distinguish from the US format
>
> France uses day/month/year as well.
Really? OK, learned something new then...

>>> As compared to the big endian notation year.month.day used for example
>>> in Japan,
>> The most sensible IMHO, makes sorting easiest.
>
> As long as year, month and day are formated with a fixed number of digits
> ;-)
Very true

>>> Yet in German, the reading order is different again: 42 is pronounced
>>> zwei und vierzig, big endian writing, little endian reading (for 2
>>> digits only ;-)
>> Actually for the last 2 digits of every number greater then 12.
>
> And for the low digit pairs in every group of three for larger numbers.
Ah, yes, indeed. As I said: a confusing and (therefor) broken concept...

"Charlie Gordon" <news@chqrlie.org> writes:

> "Richard Heathfield" <rjh@see.sig.invalid> a écrit dans le message de news:
> t_KdnR8gONyx4ZfanZ2dnUVZ8taknZ2d@bt.com...
> <snip>
>> "Big endian" means that the most significant values come first in the
>> underlying representation. A good example is prices in a shop: when we see
>> 39.99 on a pair of jeans, we know that it's about 40 currency units, not
>> almost a hundred currency units. "Little endian" means that the least
>> significant values come first - and I suppose the obvious example would be
>> UK date format: day/month/year.
>
> As compared to the big endian notation year.month.day used for
> example in Japan, and the braindead endian mixup month/day/year used
> in the USA.
>
> Lets refine your currency example: numbers are written in big endian decimal
> representation in English, but the same ordering of the digits in Arabic is
> indeed little endian.

.... in most of the original ancient forms the "denomination" (sheaves
of wheat, cattle, talents of silver) came, quote reasonably, after the
number in the reading order. Hence writing £39.99 is a nod to the
little-endian origin of the numbers.

--
Ben.

Joachim Schmitz wrote:
> "Charlie Gordon" <news@chqrlie.org> schrieb:
>> "Richard Heathfield" <rjh@see.sig.invalid> a écrit:
>>
.... snip ...
>>
>>> UK date format: day/month/year.
>
> Same format in the rest of Europe, only a different separator:
> day.month.year
> The UK format is pretty hard to distinguish from the US format
>
>> As compared to the big endian notation year.month.day used for
>> example in Japan,
>
> The most sensible IMHO, makes sorting easiest.
>
>> and the braindead endian mixup month/day/year used in the USA.

Why do people keep using these obsolete formats, when there exists
an ISO standard for the operation (close to the Japanese format)?

--
Chuck F (cbfalconer at maineline dot net)
Available for consulting/temporary embedded and systems.
<http://cbfalconer.home.att.net>


--
Posted via a free Usenet account from http://www.teranews.com

"Joachim Schmitz" <nospam.jojo@schmitz-digital.de> writes:
> "Charlie Gordon" <news@chqrlie.org> schrieb im Newsbeitrag
> news:47195862$0$24602$426a34cc@news.free.fr...
[...]
>> As compared to the big endian notation year.month.day used for example in
>> Japan,
> The most sensible IMHO, makes sorting easiest.

ISO 8601 specifies YYYY-MM-DD; for example, today is 2007-10-20. It's
the format I use whenever I have a choice.

--
Keith Thompson (The_Other_Keith) kst-u@mib.org <http://www.ghoti.net/~kst>
San Diego Supercomputer Center <*> <http://users.sdsc.edu/~kst>
"We must do something. This is something. Therefore, we must do this."
-- Antony Jay and Jonathan Lynn, "Yes Minister"

"Ben Bacarisse" <ben.usenet@bsb.me.uk> a écrit dans le message de news:
87prz9c0xx.fsf@bsb.me.uk...
> "Charlie Gordon" <news@chqrlie.org> writes:
>
>> "Richard Heathfield" <rjh@see.sig.invalid> a écrit dans le message de
>> news:
>> t_KdnR8gONyx4ZfanZ2dnUVZ8taknZ2d@bt.com...
>> <snip>
>>> "Big endian" means that the most significant values come first in the
>>> underlying representation. A good example is prices in a shop: when we
>>> see
>>> 39.99 on a pair of jeans, we know that it's about 40 currency units, not
>>> almost a hundred currency units. "Little endian" means that the least
>>> significant values come first - and I suppose the obvious example would
>>> be
>>> UK date format: day/month/year.
>>
>> As compared to the big endian notation year.month.day used for
>> example in Japan, and the braindead endian mixup month/day/year used
>> in the USA.
>>
>> Lets refine your currency example: numbers are written in big endian
>> decimal
>> representation in English, but the same ordering of the digits in Arabic
>> is
>> indeed little endian.
>
> ... in most of the original ancient forms the "denomination" (sheaves
> of wheat, cattle, talents of silver) came, quote reasonably, after the
> number in the reading order. Hence writing £39.99 is a nod to the
> little-endian origin of the numbers.

Again, this is subject to cultural differences. In French, for example,
prices are usually written with the euro sign after the number,and
pronounced accordingly: "Ce logiciel est au prix de 21 ?"

--
Chqrlie.

In data Sat, 20 Oct 2007 03:22:42 +0200, Charlie Gordon scrisse:
>"Richard Heathfield" <rjh@see.sig.invalid> a écrit dans le message de news:
>t_KdnR8gONyx4ZfanZ2dnUVZ8taknZ2d@bt.com...
><snip>
>> "Big endian" means that the most significant values come first in the
>> underlying representation. A good example is prices in a shop: when we see
>> 39.99 on a pair of jeans, we know that it's about 40 currency units, not
>> almost a hundred currency units. "Little endian" means that the least
>> significant values come first - and I suppose the obvious example would be
>> UK date format: day/month/year.
>
>As compared to the big endian notation year.month.day used for example in
>Japan,
>and the braindead endian mixup month/day/year used in the USA.
>
>Lets refine your currency example: numbers are written in big endian decimal
>representation in English, but the same ordering of the digits in Arabic is
>indeed little endian. The digits are different and the reading order is
>still big endian though. Yet in German, the reading order is different
>again: 42 is pronounced zwei und vierzig, big endian writing, little endian
>reading (for 2 digits only ;-)

the numbers for a computer are all little endian

if i have to do in decimal

0 0 9+
0 0 1
---------
0 0 0 1

you see the number grow in the right direction of memory
(if you see a potiner to 0 0 0 1 memory)

otherwise if the memory limit is found i know it

"RoS" <Ros@not.exist> a écrit dans le message de news:
vomei3h03qr3v4purfnu6fa2fi265u341o@4ax.com...
>
> the numbers for a computer are all little endian
>
> if i have to do in decimal
>
> 0 0 9+
> 0 0 1
> ---------
> 0 0 0 1
>
> you see the number grow in the right direction of memory
> (if you see a potiner to 0 0 0 1 memory)
>
> otherwise if the memory limit is found i know it

Little endian is definitely a more effective approach for computing variable
size bignums and bit arrays, etc. But it is less straight forward when it
comes to comparing these bignums ;-)

--
Chqrlie

RoS <Ros@not.exist> writes:
[...]
> the numbers for a computer are all little endian
[...]

Wrong.

Are you "RoSsIaCrIiLoIA"? If so, apparently you're changing your name
to avoid killfiles. Please stop; it's rude.

--
Keith Thompson (The_Other_Keith) kst-u@mib.org <http://www.ghoti.net/~kst>
San Diego Supercomputer Center <*> <http://users.sdsc.edu/~kst>
"We must do something. This is something. Therefore, we must do this."
-- Antony Jay and Jonathan Lynn, "Yes Minister"