Revision as of 13:47, 10 August 2009

CPP

CPP is the C preprocessor, which is also the C++ preprocessor, which processes the macros for both languages. Why not treat it as a language in itself? It is possible to run the preprocessor as a standalone language processor. Examples with macros in C++ and examples with macros in C (e.g., 99 Bottles of Beer) seem to be either duplicates or very similar.

If CPP is added as separate language, I think it would be better to call it "C preprocessor". Those acronyms tend to be obscure. --PauliKL 13:47, 10 August 2009 (UTC)

Language vs Dialect

I think this collection is getting just a little out of hand - should this be sub-categorized somehow? Do we really need Visual Basic and Visual Basic .Net and VB.net (is that just redundant)? In addition to BASIC and FreeBASIC? Does it make sense to have MySQL and PostgreSQL entries? I would bet that MIRC is the same as MIRC scripting language. This whole listing here just looks kinda helter-skelter. Sgeier 18:44, 1 February 2007 (EST)

Addendum: I also notice LISP vs Common Lisp vs Scheme.Sgeier 18:49, 1 February 2007 (EST)

Common Lisp and Scheme are certainly different. Maybe LISP is for solutions common to either? or for the ancient Lisp dialects? Good question. --IanOsgood 17:43, 16 November 2007 (MST)

add SDL

Since this language aready has tasks solved it should be added to the Solutions by Programming Language section!

SDL isn't a programming language, it's a library which makes tasks like GUI development easier. --Short Circuit 23:28, 9 February 2007 (EST)

I've discovered today that SDL is even a language (Simple Declarative Language); unlucky clashing. I suppose that if someone one day will add code for SDL (language), we should rename SDL (the library) to something like libSDL ... --ShinTakezou 10:06, 10 August 2009 (UTC)

C plus plus

There's still two different entries here - One for "C plus plus" and one for "C++". Sgeier 00:48, 20 February 2007 (EST)

Finally fixed.

Bash vs. Shell vs. Unix Shell

Is this list an index or a proscriptive sort of list? Because I just wandered in looking for a reminder how to do some task X in BASH and couldn't find it. Went elsewhere, solved my needed task, then came back to figure out WTF. Searching on 'bash', I found *plenty* of references to BASH, and via them the 'Unix Shell' element on 'Solutions by Programming Language'.

So... if this is a user-friendly index, some entries like 'Bash' and/or a 'Shell' entry that then disambiguates to all the shell scripting languages might be helpful. Heck, just adding plain text under 'B' that said: BASH (see Unix Shell) would have been sensible.

Bash now redirects to Bourne Again SHell. --IanOsgood 17:39, 16 November 2007 (MST)

@@ Line 2: / Line 2: @@
 CPP is the C preprocessor, which is also the C++ preprocessor, which processes the macros for both languages.
 Why not treat it as a language in itself? It is possible to run the preprocessor as a standalone language processor. Examples with macros in C++ and examples with macros in C (e.g., [[99 Bottles of Beer]]) seem to be either duplicates or very similar.
+:If CPP is added as separate language, I think it would be better to call it "C preprocessor". Those acronyms tend to be obscure. --[[User:PauliKL|PauliKL]] 13:47, 10 August 2009 (UTC)
 =Language vs Dialect=