| ??? 05/09/12 22:03 Read: times |
#187307 - Interreted Languages - revisited |
In an old, now locked, thread, I said:
One of the oft-claimed advantages of Interpreted Languages is that you don't have the overhead of the "build" cycle.
As I'm currently working with an Interpreted Language (Python - not on an 8051), I'm coming to think that this is not (necessarily) all it's cracked-up to be: http://www.8052.com/forumchat/read/184656 It seems that TI are now suffering from exactly this problem on their forum: I said:
The error is that a method or property is being used which doesn't exist!
Now, a compiled language would give a compile-time error for that - surely, there must be tools to detect this for a scripting language...?! http://e2e.ti.com/group/hel...spx#673632 |
| Topic | Author | Date |
| Interreted Languages - revisited | 01/01/70 00:00 | |
| No Tools? | 01/01/70 00:00 | |
| Interpreted is always problematic for complex problems | 01/01/70 00:00 | |
| It's more than just syntax | 01/01/70 00:00 | |
| lint isn't really a syntax checker | 01/01/70 00:00 | |
| Yea That | 01/01/70 00:00 | |
| Static code analyser | 01/01/70 00:00 | |
| Exception handling | 01/01/70 00:00 | |
| exceptions are normally too little too late | 01/01/70 00:00 | |
| the issue with interpreted languages is ... | 01/01/70 00:00 | |
| interpreted languages are more than "throw away code" | 01/01/70 00:00 | |
| I hate throwing objects in the cogs, but... | 01/01/70 00:00 | |
| Someone else responsible for compiling the interpreter | 01/01/70 00:00 | |
But the same applies to compiled languages! | 01/01/70 00:00 | |
| Disagree | 01/01/70 00:00 |



