Talk:Boxing (computer programming): Difference between revisions

Content deleted Content added
Def, scope, mess: afterthought
Line 71:
:: So, I think the best solution is to rename this article to [[Boxing, unboxing and autoboxing]] and add a [[WP:SUMMARY]] of this at [[primitive types]] and at [[object (computer science)]]. [[User:Pohta ce-am pohtit|Pcap]] [[User_talk:Pohta ce-am pohtit|<small>ping</small>]] 07:01, 27 August 2009 (UTC)
::: After a little more thought, these are not just implementation issues, but design too. Whether you force the programmer to write boilerplate code for boxing/unboxing or decide to go for autoboxing is a language design issue as well. Still, this doesn't change the fact that this article is about the relation between primitive types and object types in OOP languages. [[User:Pohta ce-am pohtit|Pcap]] [[User_talk:Pohta ce-am pohtit|<small>ping</small>]] 07:11, 27 August 2009 (UTC)
 
I agree that ''currently'' the content of the article is inconsistent with the title. So, the simplest solution, I guess, is to rename it. But I'm afraid the name [[Boxing, unboxing and autoboxing]] may narrow the scope of the article too much. The article starts with saying that an object type is a datatype, and so it should be about a general concept, mentioning boxing of a primitive data type as one example, not as a primary subject. The lack of a precise definition is not a good reason for not to have an article. For example, an [[interpreted language]] doesn't give a precise definition, but tries to cover context and give a lot of examples. In short, "Object type" may be too vague to be a good title. But "[[boxing, ...]]" doesn't seem a good one, either. Maybe someone can propose a better title. -- [[User:TakuyaMurata|Taku]] ([[User talk:TakuyaMurata|talk]]) 11:57, 27 August 2009 (UTC)