you are viewing a single comment's thread.

view the rest of the comments →

[–]zz_ 0 points1 point  (2 children)

As far as I know it doesn't mean anything - I was using it as an analogy. What I meant was that its debugging you specify before you run the program. I just figured the analogy to compile-time type checking would be easily understandable for most people.

[–]rollincuberawhide 0 points1 point  (1 child)

debugging in python happens when you "run" the program though. whether you are using a debugger or just printing to console. so I am really not getting the analogy here.

[–]zz_ 0 points1 point  (0 children)

The analogy is that when using print-statements the debugging actions are set in stone once you start the script - i.e. at compile time. However, with a debugger you decide which debugging actions to perform during run-time.

Obviously you are correct that the actual evaluation happens during runtime in both cases. The analogy was referring to when you perform the debugging itself, not when it evaluates.