> and in C we now have 'float' for the single precision 32 bit IEEE 754
type,
> 'double' for the 64 bit type and 'long double' for 80 bit type
Is there an 64bit integer type on all platforms? It tryed "long long int" in
C, but it seemed it didn't work (Linux nor w2k, but I'm not sure, could also
Jesus M. Castagnetto wrote:
>In fortran (and other langs), float was 16 bit and
>double 32 bit (IIRC). Some newer langs and scripting
>ones use the double width for either.
>
and in C we now have 'float' for the single precision 32 bit IEEE 754 type,
'double' for the 64 bit type and 'long double'
On Thu, 20 Sep 2001, Jesus M. Castagnetto wrote:
> Just a short 2 cents:
> double is referred to number that is a floating point
> with double precision, i.e. twice as many bits are
> used to store as it is used for regular floating point
> numbers (called float).
>
> In fortran (and other langs
> > so no reasons left for not calling a floating point
> > number
> > "float" instead of "double" (double what?)
>
> double is referred to number that is a floating point
> with double precision, i.e. twice as many bits are
> used to store as it is used for regular floating point
> numbers (call
Just a short 2 cents:
--- Hartmut Holzgraefe <[EMAIL PROTECTED]> wrote:
> Hartmut Holzgraefe wrote:
> > the only reason for not changing 'double' to
> 'float'
> > all over the place are is_double() (which could be
> aliased)
> > and gettype() returning "double" as a type
> identifier string
> > wh
Hartmut Holzgraefe wrote:
> the only reason for not changing 'double' to 'float'
> all over the place are is_double() (which could be aliased)
> and gettype() returning "double" as a type identifier string
> which is not easy to change without breaking existing code
but then the gettype() page al
Egon Schmid wrote:
> I also don´t see any problems to use floats and
> doubles in the manual.
so inconsistencies are a good thing?
IMHO^H^H^H^Hdefinetly not!
PHP has only one floating point type,
so there should be only one name for it
for historical reasons it has been called 'double'
as is
On Thu, 20 Sep 2001, Egon Schmid wrote:
> problems with it. I also don´t see any problems to use floats and
> doubles in the manual.
Do you mean to use both together?
I think that for the sake of consistency it is best to stick to one
variant. That's also the primary reason why I mailed.
Realit
> On Thu, 20 Sep 2001, Egon Schmid wrote:
> > It is not very polite to change the readme and force editors and
> > authors using an "official" name for a cast.
[...]
> (The point was simply that IMHO we should use (float), and I
assumed and
> assume that Stig didn't know of it. When he reads th
On Thu, 20 Sep 2001, Egon Schmid wrote:
> It is not very polite to change the readme and force editors and
> authors using an "official" name for a cast.
I don't force anyone to use (float) in stead of (double), but we did
have a small discussion on it, and it ended up in being (float).
If someo
> > +return ((double)$sec+(double)$usec) * 10;
>
> The official name for the cast is 'float'. I know, the
documentation is
> still very inconsistent, but the language section is more or less
okay
> now.
>
> See also the readme on type names.
It is not very polite to change the readme and
> +return ((double)$sec+(double)$usec) * 10;
The official name for the cast is 'float'. I know, the documentation is
still very inconsistent, but the language section is more or less okay
now.
See also the readme on type names.
Greetz,
Jeroen
-- Webmasters A-Eskwadraat <[EMAIL PROTECTE
Egon,
DOCBOOK-XML, look into the result!
If the first parameter is optional, the second parameter is also optional!
Please look at bug #12550, look what I and you have done, and correct it.
Regards,
Thomas
Egon Schmid wrote:
> eschmid Mon Aug 6 23:38:28 2001 EDT
>
> Modified
13 matches
Mail list logo
