> SS> Yes, but now you have to told to FB explicitly which part of number have
> SS> to be discarded.
>
> And you still could do this, as you wish :) You remain with full
> control, if/when you prefer to have it. I guess the proposed
> enhancement will be useful for 99% of the cases, when user don
This link may be useful to such a discussion:
http://speleotrove.com/decimal/
It's been around a long time, so you may already be familiar
with it. A project I have been involved with wrote a system
based on that reference library storing 34 digit numbers in
text fields (with appropriate collatio
> -Original Message-
> From: Carlos H. Cantu [mailto:lis...@warmboot.com.br]
> Sent: Lunes, 07 de Diciembre de 2015 21:40
>
> SS> The final solution will be support for high precision arithmetics.
> SS> https://en.wikipedia.org/wiki/Arbitrary-precision_arithmetic
>
> Maybe. But will some
The original Interbase implementation had rational, aka reasonable,
arithmetic semantics.Your example is an excellent example of idiotic
semantics. Borland rewrote the code to conform what they, severely
lacking in working neurons, interrupted the SQL standard to require.
I care very littl
SS> Yes, but now you have to told to FB explicitly which part of number have
SS> to be discarded.
And you still could do this, as you wish :) You remain with full
control, if/when you prefer to have it. I guess the proposed
enhancement will be useful for 99% of the cases, when user don't care
abo
> SS> 1. Decimal or Numeric is used for to keep exact accuracy.
> SS>If you don't need this accuracy use float point data types.
>
> You didn't get the point. There is no loss of accuracy. The data types
> will continue working as is. Remember, as I said, today you already have to
> cast
> if
I have several points against this idea:
1. Decimal or Numeric is used for to keep exact accuracy.
If you don't need this accuracy use float point data types.
2. System that will produce unpredictable results in math is really hard
to use.
Some numbers will rounded, truncated or modified.
SS> I have several points against this idea:
You opinion is welcome :)
SS> 1. Decimal or Numeric is used for to keep exact accuracy.
SS>If you don't need this accuracy use float point data types.
You didn't get the point. There is no loss of accuracy. The data types
will continue working as
I know there are plans to support long numbers in Firebird. I have no
idea what is the schedule for its implementation or how much this
subject has been discussed before. Anyway, this email is not to
discuss long numbers implementation, although the subject can be more
or less related.
I want to d
Can be handy when doing crossplatform builds
http://blogs.msdn.com/b/vcblog/archive/2015/12/04/introducing-clang-with-microsoft-codegen-in-vs-2015-update-1.aspx
--
Go from Idea to Many App Stores Faster with Intel(R) XDK
G
big +1
regards,Karol Bieniaszewski
Oryginalna wiadomość
Od: Adriano dos Santos Fernandes
Data: 06.12.2015 23:38 (GMT+01:00)
Do: For discussion among Firebird Developers
Temat: Re: [Firebird-devel] Firebird #.## msg file
In 99% time, database engine messages are no
11 matches
Mail list logo
