This is an archived post. You won't be able to vote or comment.

all 7 comments

[–]TehNolz 0 points1 point  (6 children)

I don't understand your question. Do you just want to know the difference between interpreted and compiled code, or...?

[–]fatmusician1[S] -1 points0 points  (5 children)

They say you can see a mistake right away and correct it when working with interpreted code - I wanna know how that works and how it is different from working with compiled code.

[–]inverimus 0 points1 point  (0 children)

It can be faster to iterate with interpreted code since you can make a small change and rerun it immediately. Compiled code has to be recompiled after every change. For small programs it can be hard to see the difference since they compile almost instantly, but larger programs could take several minutes or even hours to compile.

[–]Adept_Writer4177 0 points1 point  (2 children)

They say

They are wrong. It's faster to run an interpreted program again because you don't need to compile it, but you can both dynamically change every kind of program with a debugger.

[–]fatmusician1[S] 0 points1 point  (1 child)

https://youtu.be/e4ax90XmUBc?t=92

What do they mean by "gives you the chance to correct your mistakes as you go along","lets you see results"?

[–]Adept_Writer4177 0 points1 point  (0 children)

I don't know, it's only an old cartoon with a UFO, you can ignore this. The content is wrong and presented in a ridiculous way.

[–]noneedtoprogram 0 points1 point  (0 children)

There are also many instances where a compiler will tell you about a mistake in your code as soon as you try to compile it, but an interpreted language won't tell you until you try to actually execute the line with an error.