Wed, 16 Apr 2003 14:03:35 -0300
> Great! I'll work on it.
> How should we do to avoid compatibility problems? Some solutions that
> come into my mind are:
> - Forget about it completely and fix the syntax handling to be
> posix compliant.
> - Create a subclass of shlex, or a completely different class
> (shlex_posix?) depending on how much can be reused.
> - Add a flag to the constructor.
Thinking further about this, I belive there's a better solution. I'll
write different functions (probably read_word()/get_word()) with the
[ 2AAC 7928 0FBF 0299 5EB5 60E2 2253 B29A 6664 3A0C ]