I create an environment variable. Then I use getenv() to check for its existence. This gives me the ability to turn on some debugging features at my customer’s site even if they are running the runtime version.

>I am wrestling with determining best practice for setting class properties that may change based on whether the class is being run in development or deployment. An example of this is a property in the class that turns on the unwinding of a collection into an array. Useful during development so you can see what the heck is in the collection, but a waste of time in deployment when I would like the property turned off.
>
>(Minor gripe ... why can't the debugger let us expand a collection? Otherwise LOVE the collection class!)
>
>Currently I am actually changing the property depending on which mode I am in dev vs deploy. I would like to set this information independently of the class and read the information in, for this and several other properties.
>
>The places that occur to me to do this are in a:
>1.) ini file
>2.) system parameter dbf
>3.) .h file
>
>What do others do and what are the benefits of the separate approaches?