Re: [DISCUSS][C++] Can we use "0E+1" not "0.E+1" for deciaml for broader compatibility?

2024-10-01 Thread Sutou Kouhei
ew issue for it: https://github.com/apache/arrow/issues/44285 Thanks, -- kou In "Re: [DISCUSS][C++] Can we use "0E+1" not "0.E+1" for deciaml for broader compatibility?" on Tue, 1 Oct 2024 10:50:41 +0200, Jacek Pliszka wrote: > Hi! > > I am a bit puzz

Re: [DISCUSS][C++] Can we use "0E+1" not "0.E+1" for deciaml for broader compatibility?

2024-10-01 Thread Antoine Pitrou
Hi Kou, That sounds fine to me. Regards Antoine. Le 01/10/2024 à 03:55, Sutou Kouhei a écrit : Hi, The current decimal implementation omits the fractional part if the fractional part is 0. For example: "0.E+1" not "0.0E+1" Most environments such as Python, Node.js, PostgreSQL and MySQL a

Re: [DISCUSS][C++] Can we use "0E+1" not "0.E+1" for deciaml for broader compatibility?

2024-10-01 Thread Jacek Pliszka
Hi! I am a bit puzzled why it is not 0e0. This seems to me the "natural" way 0 should be written in scientific notation. Best Regards, Jacek Pliszka > Le 01/10/2024 à 03:55, Sutou Kouhei a écrit : > > Hi, > > > > The current decimal implementation omits the fractional part > > if the fractio

[DISCUSS][C++] Can we use "0E+1" not "0.E+1" for deciaml for broader compatibility?

2024-09-30 Thread Sutou Kouhei
Hi, The current decimal implementation omits the fractional part if the fractional part is 0. For example: "0.E+1" not "0.0E+1" Most environments such as Python, Node.js, PostgreSQL and MySQL accepts "0.E+1" but some environments such as Ruby don't accept "0.E+1". Can we use "0E+1" (omit "." and