Talk:Type conversion

message: c#, Java, Perl, Haspell, javascript, Coffescript, Haxe, livescript, Lua, Ruby, Closure, Scala, etc
 - strong/weak, declaration necessary/optional/possible, inference, implicit typing, strict/dynamic,  implicit conversion,...
Perhaps another new article?  — Preceding unsigned comment added by 91.113.38.50 (talk) 19:23, 9 February 2014 (UTC)
thread_title:  Table for programming languages 

message: It seems like the sections related to Eiffel are much larger than they should be, given the relative level of popularity of Eiffel. It would be more useful to show type conversion in other languages instead of so much on a fairly obscure language. In my opinion the long discourse of Eiffel's type conversion should go on an Eiffel page, or better yet, a new page.
Smithderek2000 (talk)  —Preceding undated comment added 00:04, 22 September 2012 (UTC)
thread_title:  Overemphasis of Eiffel 

message: The section on implicit type conversion contained false and misleading statements:
* "For example, in the above comparisons, there would be a loss of information in a conversion from type double to type int if the value of d is larger than i can hold."
*: False. The comparisons listed do not involve any conversion from double to int, but the other way around. Actually, any comparison involving a double and an int will have the int promoted to double, not the other way around.
* Conversely, converting from an integral representation to a floating-point one can also lose precision, as floating-point representations are generally not capable of holding integer values precisely.
*: Inaccurate. What is true is that a floating-point representation of n bits can never hold all integer values of n bits precisely, since there's just not enough room for both the exponent and the significand. However, an IEEE 754 double precision type is capable of representing all 32-bit integer values exactly, for example, so this statement is misleading, especially in the given context. 82.95.254.249 18:12, 29 March 2007 (UTC)
replies: text: There's an inaccuracy in this part: "long int to int causes dropping of excess higher order bits."  That's only true if long int is a different size than int.  In DOS environments, int is typically 16-bit and long int 32, and in some 64-bit environments int is 32 and long is 64.  In those cases, the statement holds.  However, in many 32-bit environments and some 64-bit environments, int is the same as long int at 32 bits or 64 bits (respectively), making that statement unreliable.  Is there a better way of saying that, that we could include in the text? Renegrade (talk) 03:49, 21 October 2011 (UTC)
thread_title:  Inaccuracies 

message: Old merge proposal that hasn't been formally discussed. No opinion. Pairadox 04:33, 28 August 2007 (UTC)
replies: text: Should be merged to an article on C++ casting operators (or C++ operators), if there is and should be such an article.  If I find one I'll update that merge tag.  — The Storm Surfer 22:58, 29 August 2007 (UTC)
replies: text: static_cast was an individual article, then without discussion and reasons given was changed to redirect to this article. I reverted the static_cast article back to its content before redirection. --Abdull (talk) 21:39, 1 October 2010 (UTC)
thread_title:  Merge from [[static_cast]] 

message: I think that the information from the atoi and atof articles should be included. Any thoughts? --208.138.31.76 (talk) 15:38, 23 January 2008 (UTC)
replies: text: I agree, IMHO we should go even further and make an article like Functions converting from ASCII in standard ANSI C library (with a better name of course) and merge atoi, atof, strtod, etc... Miko3k (talk) 00:45, 22 May 2008 (UTC)

text: I disagree with the inclusion because this article is theoric. But creating an article merging atoi, atof, strtod, etc... is a good idea  —Preceding unsigned comment added by 82.231.158.89 (talk) 16:59, 4 June 2008 (UTC)

text: I disagree, atoi and other related functions belong to one particular programming language and this is a general article. 195.226.8.98 (talk) 11:43, 3 September 2008 (UTC)

text: I also disagree, to me, atoi and related _functions_ are not even type conversion. (Type here being the concept of type as used by compilers). They are simply utility functions that take a string as an input and return an integer (e.g. atoi). There is absolutely no relation between the input passed in and the output generated, other than we hope that they in some way refer to the same value, but that depends on how we interpret that value (what I mean is that there is some form of implicit 'format convention' necessary, as to how numbers can be represented as text.  —Preceding unsigned comment added by 123.27.219.212 (talk) 12:39, 23 February 2010 (UTC)
thread_title:  Merge from ato* 

message: In languages like Pascal (programming language) conversion and casting are distinctly different concepts. This article takes a rather C-centric view.
Conversion refers to either implicitly or explicitly changing a value from one data type to another, e.g. a 16-bit integer to a 32-bit integer. The storage requirements may change as a result of the conversion. A loss of precision or truncation may also occur.
Casting refers to explicitly changing the interpretation of the bit pattern representing a value from one type to another. For example 32 contiguous bits may be treated as an array of 32 booleans, a two character Unicode string, an unsigned 32-bit integer or an IEEE single precision floating point value. The storage requirements are never changed by a cast. Casting requires an intimate knowledge of the byte order of the system and an awareness of any alignment requirements.
RegulatorRectifier (talk) 17:58, 4 December 2008 (UTC)
thread_title:  Conversion vs Casting 

message: Does anyone know if this article has to do with the properties of 'variant' types in VB and VBA? A variant variable can be any other type of variable at any point of an algorithm, but I don't have the knowledge to assert that is the same as this article. Khullah (talk) 00:07, 29 November 2011 (UTC)
thread_title:  Visual Basic 

message: const_cast redirects here, but is not explained in the article.  -- Juergen 62.143.196.71 (talk) 14:56, 7 November 2015 (UTC)
thread_title:  const_cast 

message: * int i_value   = 16777217;
Ain't it within [- 32767(?) to 32767] ?!
* 
double  d;
long    l;
int     i;
if (d > i)   d = i;
if (i > l)   l = i;
if (d == l)  d *= 2;
What is being compared? There are no any values, there are no sizeof-s...
Oleg Ostapchuk 15:18, 10 February 2019 (UTC)
thread_title:  Strange codes 

message: This page and  Typecasting (disambiguation)  render "type casting" in computer programming as two words, with no alternate listed. But at least two of the references render it as one word.  — Preceding unsigned comment added by 137.79.225.147 (talk) 18:35, 20 September 2023 (UTC)
thread_title:  One word or two?