Skip to main content
Software Engineering

Return to Question

Tweeted twitter.com/#!/StackProgrammer/status/612054932494155777
Post Reopened by Karl Bielefeldt, Bart van Ingen Schenau, psr, ChrisF
Post Closed as "Needs more focus" by gnat, CommunityBot, durron597
fixed title
Link
edit approved Jun 2, 2015 at 20:02
null
edit approved Jun 2, 2015 at 20:02
null
  • 3.8k
  • 1
  • 14
  • 21

What stops C from being being compiled/interpreted/JIT'ed?

edited title
Source Link
Robert Harvey
Robert Harvey
  • 200.7k
  • 55
  • 470
  • 683

What stops C compiling vs interpretingfrom being being compiled/interpreted/JIT'ed?

Java is often praised for its amazing portability, which I presume is because of the JVM. My question is what stops C from being being compiled/interpreted/JIT'ed.., if so, C can also be write once and have it work on what ever device you have. but this is not a popular mechanism for processing a C program. 

What are the disadvantages of processing C in this way, also what are the advantages of processing Java in this way and not compiling to machine code, other than the portability of course. I am a bit confused about this topic. Any help is appreciated.?

C compiling vs interpreting

Java is often praised for its amazing portability, which I presume is because of the JVM. My question is what stops C from being being compiled/interpreted/JIT'ed.., if so, C can also be write once and have it work on what ever device you have. but this is not a popular mechanism for processing a C program. What are the disadvantages of processing C in this way, also what are the advantages of processing Java in this way and not compiling to machine code, other than the portability of course. I am a bit confused about this topic. Any help is appreciated.

What stops C from being being compiled/interpreted/JIT'ed?

Java is often praised for its amazing portability, which I presume is because of the JVM. My question is what stops C from being being compiled/interpreted/JIT'ed.., if so, C can also be write once and have it work on what ever device you have. but this is not a popular mechanism for processing a C program. 

What are the disadvantages of processing C in this way, also what are the advantages of processing Java in this way and not compiling to machine code, other than the portability of course?

Source Link
SphericalCow
SphericalCow
  • 223
  • 1
  • 7

C compiling vs interpreting

Java is often praised for its amazing portability, which I presume is because of the JVM. My question is what stops C from being being compiled/interpreted/JIT'ed.., if so, C can also be write once and have it work on what ever device you have. but this is not a popular mechanism for processing a C program. What are the disadvantages of processing C in this way, also what are the advantages of processing Java in this way and not compiling to machine code, other than the portability of course. I am a bit confused about this topic. Any help is appreciated.