Currently, if you write something like this:

debug = x;

It's like you passed -debug=x on the command line. However, this seems quite scary. It means that you are debugging ALL THE TIME, with any debug(x) statements.

Does this make sense? Note that debug disables pure checking, which can be dangerous. I'm kind of uneasy that if I don't pass any debug arguments to the compiler, it can still violate purity in the name of debugging with such statements.

I would have expected debug = x to only be enabled when -debug is passed to the compiler. Does this make sense to anyone?

Note, there is no way to simply enable the same thing as -debug does in code.

-Steve

Reply via email to