Talk:Language Comparison Table: Difference between revisions

Paradigm links shortened!
(Paradigm links shortened!)
Line 1:
== Haskell and what makes a standard a standard ==
 
Is Haskell standardized by some standards body, ISO, IEC etc? (Language report certainly does not qualify as a standard. All languages have reports, since Algol 68 times...) --[[User:Dmitry-kazakov|Dmitry-kazakov]] 17:48, 22 July 2008 (UTC)
: No, it isn't, but the Haskell 98 Report '''is''' the standard definition for the language -- all compilers support it, and all compilers have switches to distinguish between Haskell 98 and their own extensions. Like all C compilers support ANSI C. Compare to, say, OCaml, where the current INRIA implementation of the compiler is the standard :-) Or Lisp, or Smalltalk, with their plethora of different implementations. And since it is one of the design goals of Haskell to have the language completely formally specified, I guess one should mention it somewhere.
Line 8 ⟶ 10:
::: If you for some reason want the table to contain just "official" standards, fine with me -- just clearly say so on the page, and make explicit how to find out if a standard is "official" or not. But I think for practical purposes, that would be the wrong approach: What is really interesting for a programming language is if one can rely on some common core constructs supported by virtually all implementations, and where to find the information which these constructs are. At least that's what would interest '''me''' when learning a new language.
::: Or, if you for some reason think that standards with some letters in it are "worth" more and should stand out, why not just use green/yellow/red as background? That should give people like me the information they are looking for, and keep the distinction. --[[User:Dirkt|Dirkt]] 10:31, 23 July 2008 (UTC)
 
::::It seems that you are confusing a practice with the means to enforce, codify, etc it.
::::As for RFC notes, they are edited and published by the Internet Engineering Task Force (IETF). IETF has a defined procedure of discussing and approval the documents they publish, an organizational structure, and last but not least, it declares standardization one of its goals [see [http://tools.ietf.org/html/rfc2418 RFC 2418]]. This makes IETF a standards body, and only '''so''' RFC notes standards. Implied usefulness or acceptance of RFC notes plays here no role whatsoever. --[[User:Dmitry-kazakov|Dmitry-kazakov]] 17:18, 23 July 2008 (UTC)
 
== Passing by reference in C and C++ ==
[[C]] and [[C++]] have only by-value passing mode. See an explanation in [[Parameter Passing]] --[[User:Dmitry-kazakov|Dmitry-kazakov]] 17:03, 25 July 2008 (UTC)
 
Line 120 ⟶ 122:
 
Most of the paradigm links are in the form of <nowiki>"[[{blah} programming]]"</nowiki>. Can someone script something up real quick to shorten the display title of the links by changing the wikicode to something like <nowiki>"[[{blah} programming|{blah}]]"</nowiki>? Seems like an easy Perl program, but I don't know Perl. --[[User:Mwn3d|Mwn3d]] 20:27, 9 November 2009 (UTC)
:Done. Here, for completeness, is the regex I used: <code>s/(\[\[((?:\w| |-|')+?) programming)\]\]/$1|$2]]/g</code>. —[[User:Underscore|Underscore]] ([[User talk:Underscore|Talk]]) 23:44, 9 November 2009 (UTC)
845

edits