To continue on from our CB conversation id like to see getVars() and setVars() bullet proofed. Currently its too possible to pollute the data. I propose switching to a new robust encoding (thats fast as well) and putting a version code on the strings. Something like '===01' as a magic number to start the strings (since this cant occur currently if I understand things right). Then convert to the new system on write. That way so long as folks use getVars() and setVars() they will always get their data through. This would resolve a longstanding nit of mine with settings. As I said before I had to rename Q&A_Section to QandASection to put it in the settings, likewise we've had trouble in the past with categorized answer and categorized question and underlining, deunderlining etc. Setting need/could need to store non \w chars all the time.
Sorry, a bit of free thought there for you...
First they ignore you, then they laugh at you, then they fight you, then you win.
-- Gandhi
In reply to Re: patchable settings
by demerphq
in thread patchable settings
by ysth
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |