Talk:High-level programming language

	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
???	This article has not yet received a rating on Wikipedia's content assessment scale.
???	This article has not yet received a rating on the project's importance scale.

needs cleaned up

How to mark it? But it says C "was", "might be", and then "is" a high-level language. Also, PHP isn't high-level? Really? It's interpreted, reflexive, and (somewhat) Obj-oriented. If this page is really going to say it "isn't" high-level, it needs to explain *why* (not just "it's a web language"). HTML is a markup language -- neither high nor low, because it's not a programming language. It's a document, not a program. PHP, while often used for scripts, can be used to write programs performing functions just like those of a command-line C program (but with less code). So how is PHP *not* high-level?

Well, I just removed that section, because there was little of merit in it. — mæstro ^t/c, 11:48, 1 December 2005 (UTC)[reply]

High-level programming is slightly gay?

Not sure I am interpreting this correctly. Could someone clarify?

well to be honest it is not really possible for high-level programming to be "gay." is it?

This page is wrong on so many levels. Are C and C++ really defined as High Level Languages? Sure, high level compared to machine code, but compared to Haskell, Erlang or Python? I think not. —Preceding unsigned comment added by 79.138.192.80 (talk) 00:03, 21 January 2010 (UTC)[reply]

The accepted definition of "High Level" includes all Programming Languages as we know. The limit is set at the point where is no direct translation to machine code, such as in Assembly Language (probably the unique category of "Low Level" language). "High Level" is a, now obsolete, term to indicate that you are not bounded by the concrete machine definided by you computer but rather by an abstract machine defined by your language, which is usually much more complex, even if this language is simply Fortran 0, Plankalkul or COBOL. 1. Terrence W. Pratt, Programming Languages - Design and Implementation (Englewood Cliffs, NJ: Prentice-Hall, Inc., 1981). 1. Michael L. Scott, Programming Language Pragmatics, Third Edition, 3rd ed. (Morgan Kaufmann, 2009).

~

Machine code?

anyone know how this works with machine code? Becuase I can't figure out how each instruction in high-level language corresponds to one instruction in machine code. Any one help me out? unsigned comment added by 70.62.232.146 (talk) 21:43, 24 June 2008 (UTC)[reply]

Most higher level languages compile to assembly. The compiler interprets the high level code into assembly. However, the penalty arises from the fact that you're relying 100% on the compiler for how well it does the interpreting and optimizing.

                                                                ~Jarrod1937  —Preceding

Isn't an intermediate compiler the same as a translator?

I don't understand how an intermediate compiler isn't just translating to bytecode. Since my area of expertise is much higher than this, I don't think boldness is appropriate for me. --Jesdisciple (talk) 20:11, 8 September 2008 (UTC)[reply]

Major Misconception

Interpreters and compilers are programs that process programming languages. Languages are not "interpreted" languages or "compiled" languages. Rather, language implementations use interpretation or compilation. For example, Algol 60 and Fortran have both been interpreted (even though they were more typically compiled). Similarly, Scheme has been compiled (even though it has been interpreted in most popular implementations. Java shows the difficulty of trying to apply these labels to languages rather than to implementations; Java is compiled to bytecode and the bytecode is subsequently executed by either interpretation (in a JVM) or compilation (typically with a just-in-time compiler such as HotSpot, again in a JVM). --Kdcooper (talk) 21:50, 26 August 2009 (UTC) Similarly, C# and Visual Basic.Net are compiled to MSIL then just-in-time compiled to native machine code at the time of execution (this is a different strategy than Java as tn incurs longer loading times to get the benefit of faster execution). User:Hoshantm[reply]