Re: Supplying a default initial STATE to parse-partial-sexp. What about elt. 9?

[Stefan Monnier]

> To avoid an irritating special case, I'd like to initialize the state to
> a default value, rather than passing in nil.  Something like:

I'm not sure what you mean by special case.  Usually I use nil for that
purpose and it works fine, since all the operations I use on the state
treat nil as '(nil . nil)

> However, this leaves me a bit uneasy about the 9th element, which is
> documented as "Intermediate data for continuation of parsing (subject to
> change)".  Is it valid to set elt 9 as nil, or will this cause some sort
> of malfunction or signal in parse-partial-sexp?

Yes, nil is fine there as well: it'll work just dandy!


        Stefan