World: r3wp

Btw, when a stack overflow occurs, It's terminating the console without 
sending any warning.
Did you experiment that ?

parse [ ] r: [ r ]

Vista says something bad happend, but XP just close the console.

Win 7 says
  internal error: stack overflow

Which means that stack overflows aren't being checked by PARSE. Write 
a ticket.

Went through the Parse Proposals list and tweaked the Priorities 
section to double as a status list. Unfortunately, some of the rejected 
proposals must have at some point been removed from the proposals 
page. We wanted to document them and why they were rejected, so they 
don't get proposed again. I may have to go the history and find the 
rejected proposals that were deleted and restore them to the page, 
so they can be rejected explicitly with explanations.

The main ones missing that need documented rejection are the alternatives 
to the USE and INTO proposals. The reasons they were rejected provide 
valuable information about the way PARSE works internally, information 
we don't want to lose.

The TO or THRU NOT proposals need to be restored as well, so they 
can be explicitly rejected.

Especially since they are referenced elsewhere.