Talk:Parsing/RPN calculator algorithm: Difference between revisions
(Propose making one requirement optional.) |
|||
| Line 8: | Line 8: | ||
It seems to me that the requirement that one "shows the changes in the stack as each individual token is processed as a table" is entirely extraneous to the core task of parsing and calculating RPN expressions. I think the inclusion of this kind of extraneous printing requirement goes against the principle mission of Rosetta code. For reasons outlined in [[Village_Pump/Extraneous_Printing_Requirements_in_Tasks]], I think we should make this requirement optional. If no one objects after several days, I will make this minor change. --[[User:Abathologist|Abathologist]] ([[User talk:Abathologist|talk]]) 04:09, 18 September 2016 (UTC) |
It seems to me that the requirement that one "shows the changes in the stack as each individual token is processed as a table" is entirely extraneous to the core task of parsing and calculating RPN expressions. I think the inclusion of this kind of extraneous printing requirement goes against the principle mission of Rosetta code. For reasons outlined in [[Village_Pump/Extraneous_Printing_Requirements_in_Tasks]], I think we should make this requirement optional. If no one objects after several days, I will make this minor change. --[[User:Abathologist|Abathologist]] ([[User talk:Abathologist|talk]]) 04:09, 18 September 2016 (UTC) |
||
: Could you elaborate on your thinking? --[[User:Rdm|Rdm]] ([[User talk:Rdm|talk]]) 04:28, 18 September 2016 (UTC) |
|||
Revision as of 04:28, 18 September 2016
Graduation to task
This seems to be a task that is well understood and which is attracting implementations from many different types of languages. Is there any reason to not graduate it to a full task now? –Donal Fellows 12:27, 22 January 2012 (UTC)
- Several programming examples are treating the input as characters instead of tokens, and this is working because there are no multi-digit numbers, and no numbers that contain a decimal point, and no numbers that are expressed in exponential notation (such as 3E27), and no numbers that have a leading sign, and no multi-character operands (such as **), etc. Should those programs be considered incorrect? (Just because they come up with the correct answer, doesn't make it correct. Hurrumph!) -- Gerard Schildberger 23:56, 14 December 2012 (UTC)
Extraneous Requirements
It seems to me that the requirement that one "shows the changes in the stack as each individual token is processed as a table" is entirely extraneous to the core task of parsing and calculating RPN expressions. I think the inclusion of this kind of extraneous printing requirement goes against the principle mission of Rosetta code. For reasons outlined in Village_Pump/Extraneous_Printing_Requirements_in_Tasks, I think we should make this requirement optional. If no one objects after several days, I will make this minor change. --Abathologist (talk) 04:09, 18 September 2016 (UTC)