> Le 15 févr. 2018 à 05:03, Keisuke Miyako via 4D_Tech <[email protected]> a > écrit : > >> but I'm still trying to wrap my brain around the sorts of situations that >> might require using length=0 > > as mentioned in the previous post, > there are some (non) characters that has a measurable length but whose > sorting value is equal to that of "". > Char(0) and Char(1) are such examples.
For me, 0 is invalid in unicode. About 1, I have no idea, maybe "ignorable" that seems different from invalid: $char:=Char(0x00AD) //hyphen visible only if end of line cuts the word in 2 ASSERT(Length($char)=1) ASSERT($char="") > so for all practical purposes, I wouldn't call ="" a major vulnerability. > I would though, avoid it for validating web input (because there are bad > people out there). When strings come from my code I don't hesitate, if ($myErrorText="") but when it comes from input it's another story. User is evil, and copy/paste his prophet :-) I'd like 4D to have a "strict" string comparison operator: <http://forums.4d.com/Post/FR/8090173/1/8192818#8090174> -- Arnaud de Montard ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
