If that's what you were asking, then, yes, Cervantes is right. But if it isn't, then I have the same question as you and nice observation.
Somehow, the Font.New function is very weird in that it only gets compiled if the screen is set to graphics mode! I don't think the other commands in the Font module have this weird "property". If you run this code in Turing, the Turing editor itself actually closes! Obviously, you can only draw fonts in graphics mode, but you should still theoretically be able to declare a variable using Font.New regardless of the mode of the screen.
It's not a big deal, you can't use the fonts in text mode anyways, so why not wait until it's in graphics mode to declare your variables.
But still, this is another way to crash Turing.
