Re: [pre-lexer-2 1/4] command: Factor command name matching out of command.c.

[John Darrington]

On Sat, Oct 16, 2010 at 04:27:27PM -0700, Ben Pfaff wrote:
     John Darrington <address@hidden> writes:
     
     > I've no doubt this patch is an improvement.
     > However, I'm worried about how this is going to work with non-ascii 
encodings.
     > For example some recent syntax files that I've seen have UTF-8 "hard" 
spaces 
     > (0xc2 0x0a) instead of the normal ' '.
     
     Does SPSS actually treat a "hard space" as white space?  Looking
     at the C, Java, and XML standards, none of them appear to treat
     hard spaces as white space; it appears to be rejected as invalid.
     
I can only really answer that with a question: "What do you mean by `treat as 
whitespace'"?

Based upon syntax file examples that I have found on the web, it certainly
appears to be true that a hard space is interpreted as a keyword seperator in 
syntax.

However other questions remain.  For example some comands (eg: AUTORECODE 
/MISSING )
alter their behaviour when "blank" string values are encountered. I don't
know exactly what it means for a string value to be "blank".  If anyone 
can do some experiments with spss and report the results it would be
very much appreciated.

J'

-- 
PGP Public key ID: 1024D/2DE827B3 
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See http://pgp.mit.edu or any PGP keyserver for public key.

signature.asc
Description: Digital signature