My my, you _have_ been busy   :O


Is there a way to identify and collect all of the places in source where errors
get raised, and group them by parse / render/ etc?

That might help folks get a better idea about how much there is an how often
some warnings might need to test conditions and fork flow control.

While working on the lemon, I also stumbled upon a dev manual in the 3.8 github
stuff - haven't had a chance to dig through it - might any of that already be in
there?

- BW

Post a reply to this message