Anonymous user
Talk:Parsing/Shunting-yard algorithm: Difference between revisions
Talk:Parsing/Shunting-yard algorithm (view source)
Revision as of 04:32, 30 November 2015
, 8 years ago→incorrect programs?: added whitespace and bigger font to help clarify some character strings.
m (→incorrect programs?: added whitespace and bigger font to help clarify some character strings.) |
|||
(3 intermediate revisions by 2 users not shown) | |||
Line 6:
<nowiki>{{improved}}</nowiki>! --[[User:Paddy3118|Paddy3118]] 05:47, 6 December 2011 (UTC)
==incorrect programs?==
I noticed that at least one programming example is treating the input string as characters instead of tokens. This works as long as all the numbers (and/or operators) are single characters. Would it be possible to change (shudder) the test input string specification (or add another) to include a (say) multi-digit number? If it's not reasonable to add another test case, how about changing the <big>'''4''' </big> to <big>'''004'''</big> which wouldn't affect the calculated output. Another possibility would be to change (say) the <big>'''5'''</big> to <big>'''5.'''</big> (for instance). And yet another possibility would be to add <big>'''**'''</big> as an additional exponentiation symbol (or some other compound operator). Changing the test case (or adding one) will eliminate the need for flagging the program as ''incorrect'' which I probably won't commit to doing as I really don't have any practical way to verify if the suspect program will work correctly with tokens instead of characters. -- [[User:Gerard Schildberger|Gerard Schildberger]] 06:42, 14 December 2012 (UTC)
== Improve Description ==
This seems to be about infix to RPN but it doesn't say it explicitly. --[[User:Dgamey|Dgamey]] 04:00, 13 December 2011 (UTC)
|