| ??? 05/10/12 11:37 Read: times |
#187310 - Interpreted is always problematic for complex problems Responding to: ???'s previous message |
Writing things in PHP, the majority of bugs I suffer are from spelling errors or renamed symbols.
With todays huge compiler speeds, it really is worth it to have a program do a full scan of all source code to check that the code is complete and that the different jigsaw pieces actually fits together. |
| 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 |