Re: RFC: some language issues

> > - what's the preferred name for the boolean type? > > 'bool' or 'boolean'? > > Boolean But bool in func-defs, I read in php.dev And I meant in func-defs, because the 'real' word is - of course - boolean. > > - what's the preferred name for the floating point type? > > 'double' or 'float'? > > I think that depends on the context. Technically it should be 'double', > but people don't necessarily know what 'double' means and in full > sentences I think you can use 'floating point' to discuss the type. double refers to double precision, as opposed to float, which is single-precision. since php doesn't have different floating point types (to keep it easy), you could argue that float is better, since it is just a floating point. Compare to integer: in fact, it is a long! (but since php doesn't have byte,short,int, AND long, we just call it integer, or int, because that is the REAL name. Problem: gettype now returns double... and changing that could break code (although is_double should have been used there, and that function you can keep having as an alias) Conclusion: IMO float would be better... it is the general name of that TYPE of variable. > > > - Can it be made that <type>string</type> etc will > > automagically be rendered as a hyperlink to > > language.types.string etc? Just like <function>... > > Probably > > > - language.types is such an important and large section, > > that you'll cometimes get id's like > > language.types.integer.casting.from-boolean, > > what about renaming all language.types.* to types.*? > > or type.*? > > No opinion on this one. > > -Rasmus > Jeroen