This is an old revision of this page, as edited by GeneralDenmark(talk | contribs) at 07:32, 21 February 2017(Just informed that there was a dead source :). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.Revision as of 07:32, 21 February 2017 by GeneralDenmark(talk | contribs)(Just informed that there was a dead source :)
This article is within the scope of WikiProject Computer science, a collaborative effort to improve the coverage of Computer science related articles on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.Computer scienceWikipedia:WikiProject Computer scienceTemplate:WikiProject Computer scienceComputer science
This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing
It looks like there's a lot of OR on this page. Since strong/weak typing doesn't have a single accepted definition, all examples should be backed by reliable sources, but most aren't. QVVERTYVS (hm?) 15:11, 17 June 2015 (UTC)[reply]
I've been researching the "etymology" of the terms strong and weak typing since a while. See my results so far at User:Ruud Koot/Computer science/Strong and weak typing. There isn't a universally accepted definition of those terms, but there are a small number of definitions that are often used. While contemporary researchers would rarely use these terms in a formal sense, they are still used in more colloquial speech. I think that a well-written article on this topic would be come too large to merge in its entirety into Type system (which should be an overview article, given the size of the topic). —Ruud10:58, 22 May 2016 (UTC)[reply]
I'd rather mark it as Category:Buzzwords (or similar) because it confuses so many concepts in type(s) (systems) under two words "weak" "strong" (or speakers using it).
However, we can link them in "See also" section or mention in the article from time to time. But not to crate paragraphs for these 2 words everywhere. Ushkin N (talk) 12:35, 22 May 2016 (UTC)[reply]
I think people shouldn't be using the terms strong and weakly typed, but the (unfortunate) fact is that they do. And Wikipedia is descriptive, not prescriptive, so we should discuss them. I think the section Type_system#"Strong" and "weak" type systems is fine as is. It briefly states there is no universal definition and then refers to this article for the details. I think a lot can be said here about the many non-universally accepted definitions that have been given to these terms. The section Programming_language#Weak_and_strong_typing, is more problematic. It should probably read the same as Type_system#"Strong" and "weak" type systems. —Ruud12:49, 22 May 2016 (UTC)[reply]
Criticism these 2 terms was never discussed or explained with sources.
Also any claim about "weak" or "strong" typed languages are hardly sourced since we cannot trace their definitions!
@Ushkin N, One approach to finding sources for usage would be to look up old programming books, say in Perl or C#, maybe 1995 or later. When the proponents of, say C#, were trying to push out the use of Perl (they have succeeded in lessening Perl usage) they used such terminology. Now that the debates are moot (JavaScript has increased usage, irregardless of its weakly typed status), it would probably help beginners in the field to learn what books to avoid. --Ancheta Wis (talk | contribs)14:02, 25 May 2016 (UTC)[reply]
Even if we can trace them, doesn't mean they are true. Many medal holders made imprecise statements, especially when field was rapidly developing. None of physics I know threat Newton laws as precise model of the real world, but that's off-topic here. Ushkin N (talk) 17:44, 25 May 2016 (UTC)[reply]