Mike Porter (mike@UDel.Edu) writes:
> All three group0 mean the same. Multiple quoted strings seperated
> by white space concatentate. Allowing arbitrary text to appear not
> in quotes (item1=Intel Pentium III/500) is a bad idea in my opinion
> since it raises to many escaping issues. Most people can learn
> item1='Intel "extended" Pentium III...' or
> item1="Intel ""extend... or item1="Intel \"extended...
> There are lots of ways to handle quotes in quotes. Personally, I
> would not support newline in quoted strings, it makes finding
> missing quotes and reporting them accurately to users more
> difficult.
>
> So, we end up with all white space except newline ignored, but we
> do have the line continuation character, which some people probably
> find annoying. At least it doesn't have to be in column 72.
The problem with this sort of mismash is that you spend more time writing a parser for the data than it's worth. But I guess people in this industry have forgotten KISS a long time ago. If I have to spend days writing a parser for ASCII data, my clients will hit the roof - and rightfully so.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Apr 15 2000 - 21:00:14 EST