Compiler features

Joakim Christiansen · Post by **Joakim Christiansen** » Wed May 31, 2006 6:57 pm

I see you have a EnableDebugger keyword like EnableExplicit, but it does'nt work, that's actually a bug?

I also want a EnableOnErrorsLineSupport!
So I could do:

Code: Select all

#ErrorSupport = #True
CompilerIf #ErrorSupport
  EnableOnErrorsLineSupport
  Declare Error()
  OnErrorGosub(@Error())
CompilerEndIf

Because that's just sexy!

I actually think that all compiler options should be declared like that, you know...

Code: Select all

StartCompilerOptions
  EnableExplicit
  EnableDebugger
  EnableXPSkinSupport
  EnableOnErrorsLineSupport
  SetExecutableFormat = #Windows|#AllCPU
  SetExecutableIcon = "icon.ico"
EndCompilerOptions

Trond · Post by **Trond** » Wed May 31, 2006 7:00 pm

EnableDebugger is not supposed to work the same way as EnableExplicit.

Code: Select all


DisableDebugger
  ; Do something weird here without letting the debugger know
EnableDebugger
; Do something weird here and the debugger will catch it

Joakim Christiansen · Post by **Joakim Christiansen** » Wed May 31, 2006 7:02 pm

Trond,
Oh, sorry then.

Joakim Christiansen · Mon Aug 14, 2006 11:46 pm

But what about the:

Code: Select all

StartCompilerOptions
  EnableExplicit
  EnableDebugger
  EnableXPSkinSupport
  EnableOnErrorsLineSupport
  SetExecutableFormat = #Windows|#AllCPU
  SetExecutableIcon = "icon.ico"
EndCompilerOptions

I think it would be nice, and then we don't need those hidden lines in our sourcecode:

; EnableXP
; UseIcon = icon.ico

And no it shouldn't have to be necessary to set SetExecutableFormat everytime or any of the other options, they should just have a default value.