Malcolm Tredinnick wrote:
> If you want to mark every "still needs cooking" string then you have to
> mark *every* string that comes into the system (a la Perl's tainted
> strings).
Nonono ... I just was talking about terminology. We need a term
for "safe" and "unsafe" strings. I take it as granted that you'll
only actually mark "safe" ones.
>> I'd have lots of other ideas, but feel this is getting too far.
>> How about brainstorming this on irc? Perhaps suggest a time that
>> suits you.
>
> I'll try to hang around on #django tomorrow if I don't get too busy.
> But, seriously, just come up with some good names and make people pick
> one. Stop letting people push back on your ideas and become The
> Enforcer.
Well then ... some new ideas I like:
- trusted / untrusted
- processed / unprocessed
- resolved / unresolved (with a musical connotation
processing from dissonance to consonance)
- developed / undeveloped
- fixed / unfixed (like in photo processing)
- treated / untreated
- finalized / original
- trusted / tainted (why not?)
- geared / bare
- furnished / ?
- malcomized / unmalcomized (ok, just joking ;-)
And we already have:
- safe / unsafe
- escaped / raw or unescaped
I currently have a taste for the first two, the rest is more an
invitation for others ... Now come on, native speakers, you
should be able to bring in more ideas!
Michael
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-developers
-~----------~----~----~----~------~----~------~--~---
