Hi all, It's that time again! The time you all have been waiting for! Time to put everything aside, take a deep breath, and answer the CALL! That's right, you've guessed it, it's time to VOTE!
In a neat multiple-choice quizz as you have been used to cheat to in school, your vote will decide the fate of the email address validation (issue 8436). 1. Which regexp to use for email validation? a. http://cvs.php.net/viewvc.cgi/pear/HTML_QuickForm/QuickForm/Rule/Email.php?revision=1.4&view=markup b. http://iamcal.com/publish/articles/php/parsing_email/ c. http://code.iamcal.com/php/rfc822/full_regexp.txt d. http://ex-parrot.com/~pdw/Mail-RFC822-Address.html e. http://www.tienhuis.nl/files/email_verify_source.php f. This one (please specify): _________________ g. Write our own one 2. Do we need to support conversion to Puny code (http://en.wikipedia.org/wiki/Puny_code)? a. NO WAY! b. No c. Not now d. Yes e. YES WAY! 3. If the answer to question 2 was one of c, d or e, then where to put the unicodeToPunyCode convert function (and the reverse function)? a. Mail b. Url c. Base d. UserInput e. a Tiein (please specify): _______________ f. I can tell you where to put it! 4. If the answer to question 2 was one of c, d, or e, how should the unicodeToPunyCode function be triggered? a. Automatically everytime b. Automatically if the email address contains characters outside of ASCII c. Based on a function parameter, default false d. Based on a class option, default false e. Called manually by user f. It should be hidden, with private and @ignore tags, and with an obfuscated name, so that nobody will ever know it's there and nobody will ever call it 5. How many functions which deal with email address validation should we have? a. A function which does everything (regexp, mx, punycode) in one step, with no possibility of changing the behaviour b. A function in which the parameters say if the function should do mx and punycode, which are not done by default c. A function in which the class options say if the function should do mx and punycode, which are not done by default d. 3 functions, one for each step (regexp, mx, punycode). These will be called independently e. 4 functions (the 3 functions from d and the function from b) f. 4 functions (the 3 functions from d and the function from c) g. 7 functions (regexp, mx, punycode, regexp+mx, regexp+punycode, mx+punycode, regexp+mx+punycode) All questions are mandatory (except for 3 and 4 which need to be answered only in case of c, d or e answer for question 2). There should be a maximum number of 1 (one) answer per question. Your answer should be in this form (example): 1 a 2 c 3 f (or n/a if answer to 2 was not one of c, d or e) 4 f (or n/a if answer to 2 was not one of c, d or e) 5 e The deadline for the quizz is Tuesday July 31, 09:00. Good luck! -- Alexandru Stanoi eZ Components System Developer eZ Systems | http://ez.no -- Components mailing list Components@lists.ez.no http://lists.ez.no/mailman/listinfo/components
