I confess I’m a bit confused, I thought in our PM conversation I was fairly explicit that that’s what I was asking about, and you were fairly explicit that it was forbidden?
It’s not a big deal—even if this was forbidden I’d think it would be totally fine not to disqualify simon, and I still don’t actually expect it to have been useful for me.
In my private conversation with you (philh) I stated “Writing variables to the global namespace is forbidden.” I then doubled down on the error by stating “Yes. All data must be saved in a class instance.”
I apologize for the error. What I should have written was that using the global namespace to get around information restrictions is illegal but that writing constants to your module’s global namespace in a way that does not evade information restrictions is fine.
I confess I’m a bit confused, I thought in our PM conversation I was fairly explicit that that’s what I was asking about, and you were fairly explicit that it was forbidden?
It’s not a big deal—even if this was forbidden I’d think it would be totally fine not to disqualify simon, and I still don’t actually expect it to have been useful for me.
In my private conversation with you (philh) I stated “Writing variables to the global namespace is forbidden.” I then doubled down on the error by stating “Yes. All data must be saved in a class instance.”
I apologize for the error. What I should have written was that using the global namespace to get around information restrictions is illegal but that writing constants to your module’s global namespace in a way that does not evade information restrictions is fine.