Email: Password: Remember Me | Create Account (Free)

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
Per Westermark
05/11/12 17:53
Read: 376 times
Sweden


 
#187341 - Someone else responsible for compiling the interpreter
Responding to: ???'s previous message
Justin Fontes said:
Which would mean that for every interpreter out there, the interpreter itself must have some connection to the platform. So, it is not like you can develop a brand new platform and expect to run interpreted applications without getting some support from the vendor of the interpreter. Am I wrong on this?

No. But if I write a web site in php, I don't have to care what architecture the server has - the web service can run on a Wintel machine or a Linux machine or a Solaris machine.

For people writing mobile phone applications, the phone manufacturer arranges a java environment.

Think about Android phones - there are huge variation in actual architectures but most of these architecture changes isn't important to the Java developer. With some exceptions, the java application needs to adapt to small, medium or large displays. But no need to worry what processor the phone has.

The big thing here is that the responsibility for the platform support have to a large part been shifted from application developer to the platform developer. So the application can be moved to new platforms that didn't even exist when the application was written.

I had some experience with an in house interpreter long ago, but that was a university professor project. Since then I just do not like the feel for them, as I am not into website development.

The problem with developing your own interpreted language is that you must also create the interpreter and port that interpreter to all relevant hardware.

When using an existing, larger, interpreted language, someone else will most probably take care of the porting of the interpreter.

And some interpreted languages have support for just-in-time compilation (JIT), where the interpreted program may - on some platforms - be slowly auto-converted to machine instructions without that the application developer needs to lift a finger. So in some situations, interpreted languages may reach execution speeds quite close to compiled languages. Especially since many languages have a huge set of library functions that can be compiled already from start.

List of 15 messages in thread
TopicAuthorDate
Interreted Languages - revisited      Andy Neil      05/09/12 16:03      
   No Tools?      Neil Kurzman      05/09/12 18:25      
      Interpreted is always problematic for complex problems      Per Westermark      05/10/12 05:37      
      It's more than just syntax      Andy Neil      05/10/12 15:49      
         lint isn't really a syntax checker      Per Westermark      05/10/12 17:39      
            Yea That      Neil Kurzman      05/11/12 00:08      
            Static code analyser      Oliver Sedlacek      05/11/12 03:24      
      Exception handling      Oliver Sedlacek      05/11/12 03:26      
         exceptions are normally too little too late      Per Westermark      05/11/12 04:47      
   the issue with interpreted languages is ...      Erik Malund      05/11/12 08:58      
      interpreted languages are more than "throw away code"      Per Westermark      05/11/12 12:32      
         I hate throwing objects in the cogs, but...      Justin Fontes      05/11/12 15:20      
            Someone else responsible for compiling the interpreter      Per Westermark      05/11/12 17:53      
            But the same applies to compiled languages!      Andy Neil      05/12/12 04:27      
      Disagree      Andy Neil      05/11/12 13:29      

Back to Subject List