Message99430
I haven't reviewed the patch, but if the intent is that the user can change the global, then it should not start with an _, and it should be a documented part of the API. If you want to suggest that users should not normally change it, then you can do that in the docs.
If you give something an _, then it is not considered part of the public API and it (the internal API, not the value) is subject to change, which means you should *not* suggest that users change it. If they find it and want to change it anyway, that's their lookout. That's the consenting adults part :) |
|
Date |
User |
Action |
Args |
2010-02-16 18:10:56 | r.david.murray | set | recipients:
+ r.david.murray, eric.araujo, andrewclegg |
2010-02-16 18:10:56 | r.david.murray | set | messageid: <1266343856.13.0.832760435459.issue7846@psf.upfronthosting.co.za> |
2010-02-16 18:10:54 | r.david.murray | link | issue7846 messages |
2010-02-16 18:10:54 | r.david.murray | create | |
|