Wikipedia talk:WikiProject Programming languages/Archive 1

message: A program that prints Hello Wikipedia! would be great. ;) --ZeroOne 23:13, 30 Aug 2004 (UTC)
thread_title: Sample code

message: Somehow I've got it in my head that paradigm is a good way to categorize programming languages. Here are some possible infoboxes (modeled on the impeccable Greek/Roman mythology boxes).
Proceduralprogramming languages	Proceduralprogramming languages
*C
*BASIC                     	
*Perl
Object-orientedprogramming languages	Object-orientedprogramming languages
Purely object-oriented              	Purely object-oriented
*Smalltalk                         	
*Ruby
Partially object-oriented           	Partially object-oriented
*C++                               	
*Python
Frankenstein object-oriented        	Frankenstein object-oriented
*Perl                              	
However, categorizing by heritage is also good:
C programming language family
C | C++ | Objective-C | Java | C#
List of programming languages
*Each language page should have a box of similar languages, which are grouped according to whatever classifications we choose (e.g. paradigm, heritage).
**This might involve multiple boxes though: for multiple classifications, or, for multiple paradigms, or both. That can get messy.
But, you might want to include both:
                 // opens table
   // header+rows
            // header+rows
                   // final row+closes table
This produces something like the following:
Proceduralprogramming languages	Proceduralprogramming languages
*C
*BASIC                     	
*Perl
C programming languagefamily   	C programming languagefamily
*C
*C++
*C#                   	
*Objective-C
*Java
List of programming languages  	List of programming languages
Any thoughts? --Yath 22:03, 8 Aug 2004 (UTC)
replies: text: Categorization by paradigm might not work as many languages support more than one paradigm. Categorization by heritage would probably be a better idea. Having multiple templates form a table is rather complicated unless you make one template that consists of those four templates... and I'm not sure if that's worth the hazzle. --ZeroOne 19:13, 22 Aug 2004 (UTC)
thread_title: Infoboxes

message: There was a long discussion about programming language naming conventions in Wikipedia_talk:Naming_conventions_(languages). The arguments were for and against formats "XYZ programming language" and "XYZ". According to Wikipedia:Naming_conventions_(languages) the format "XYZ" should be used always and "XYZ programming language" only in disambiguation cases. However the Wikipedia:Disambiguation#Topic articles says: 
"For creating the specific topic pages, a few options are available. If there's an alternate name or more complete name that is equally clear, that can be used. For example, Java programming language, Titan rocket."
Thus I hereby propose that all programming language articles should have the suffix "programming language" in their name. Reasoning: 
#The naming convention should be the same for all articles. Since they can't all be named "XYZ" due to some disambig issues, they should all be named "XYZ programming language". It just doesn't look professional to have "XYZ" and "ZXY programming language" side by side in lists.
#In lists like Special:Recentchanges and :Category:Stub the languages would point out nicely, attracting those who are interested in programming languages and repelling those who aren't.
#When linking it is best if you don't have to guess if the target exists or if it is a disambig page. If all languages could be linked to with "XYZ programming language" then that would save people from lots of guessing and it would also make the creation of new programming language articles easier, should the target not exist.
#How does doublefuck look like for a good christian as an article name? ;)
#My userpage wouldn't look half as cool if those language articles I created didn't have that "programming language" suffix. ;)--ZeroOne 01:10, 21 Aug 2004 (UTC)
thread_title:  Naming conventions 

message: When talking about a programming language remember that the language is a an abstract concept, and implementations of compilers or interpreters for the language is quite different.
For example, it is incorrect to say that Java is compiled to byte code. Some Java compilers compile to byte code, others compile to native object code, and it would be possible for another to translate to Python if it wanted to. It is also incorrect to say that C is compiled to native object code, as a C compiler exists for the .NET platform.
Please fully qualify what implementation of a language's compiler or interpreter you are refering to in a language's article. For example, it is fine to say that "Sun's Java compiler produces bytecode", but not simply "Java compilers produce bytecode".
:Um yeah, that's a bit confused, because the above is trivially true (thanks to stuff to do with turing machines). In real life though, it is often only practical to use a language within certain parameters. Those can certainly be named. I excised the section because it would take longer to explain all the ifs and buts and perhapses etc etc. than it would be to just be quiet about it and let things sort themselves out. I hope that explains sufficiently! :-) Kim Bruning 21:03, 29 Aug 2004 (UTC)
replies: text: The distinction between languages and implementations is still worth making though; a language article should have a sentence or two in the lead stating implementation status (one, many, none :-) ), and a section summarizing notable existing implementations, possibly with a list of links to the article-worthy. It's hard to imagine a credible PL writeup that doesn't have this kind of basic info, so I think it should be part of the requirement to have a project-conforming article. Conversely, a PL article should not say that a language is "interpreted" or "compiled", since it is a property of implementations not languages - my little title-hacking project has given me a change to observe the terrible state of PL content firsthand, and lots of articles are messed up this way. Stan 03:52, 30 Aug 2004 (UTC)
thread_title:  The difference between the language and an implementation of a compiler or interpreter 

message: Just to remind you, there's a template named  which you can (and I think should) use instead of  when dealing with programming language stubs. It produces the following message:  This computer-related article is a stub.  You can help Wikipedia by [ expanding it].
That will make it significantly easier for everybody to find and fix prog lang stubs as the :Category:Computer stubs is only one hundreth of a fraction of the size of :Category:Stubs. :) --ZeroOne 23:24, 30 Aug 2004 (UTC)
thread_title:  Stubs 

message: I just created a template  to be used with esoteric programming languages:
Notable esoteric programming languages
Befunge | Brainfuck | False | INTERCAL |
Malbolge | Shakespeare | Unlambda | Whitespace
List of esoteric programming languages | Hello world program in esoteric languages
What do you think? --ZeroOne 16:17, 31 Aug 2004 (UTC)
thread_title:  Template:Esolangs 

message: In case anyone involved with this WikiProject hasn't seen this already, there is a current deletion discussion on WP:VFD to delete 70+ articles about the more esoteric programming languages. Naturally, your input to this discussion is welcome. See Wikipedia:Votes for deletion/Esoteric programming language related. • Benc • 19:54, 29 Sep 2004 (UTC)
thread_title:  VfD listings for esoteric languages 

message: Hi,
Opinions from people knowing this subject are needed to clear a disagreement in Wikibooks. See message from Paddu belove. Thanks, Yann 20:06, 18 Nov 2004 (UTC)
thread_title:  Wikibooks C++