Talk:Strip block comments: Difference between revisions
Content added Content deleted
(→State Machine: Better definition?) |
No edit summary |
||
| Line 3: | Line 3: | ||
Note that this problem definition strongly favors a sequential state machine implementation. In particular, the example treatment for <code>/*/ stuff */</code> adds complexity to a parallel implementation. --[[User:Rdm|Rdm]] 18:25, 2 November 2010 (UTC) |
Note that this problem definition strongly favors a sequential state machine implementation. In particular, the example treatment for <code>/*/ stuff */</code> adds complexity to a parallel implementation. --[[User:Rdm|Rdm]] 18:25, 2 November 2010 (UTC) |
||
: We could bump it back to draft. Do you have a better definition? --[[User:Short Circuit|Michael Mol]] 18:40, 2 November 2010 (UTC) |
: We could bump it back to draft. Do you have a better definition? --[[User:Short Circuit|Michael Mol]] 18:40, 2 November 2010 (UTC) |
||
:I believe the intent here is to emulate the treatment of comments in existing languages. Note also that no example treatment is given for cases like <code>/*/*/*/*/*/</code> though presumably that sequence is equivalent to a single asterisk? |
|||
:In any event, I think that the specification should reflect the rigid character of the desired end. I would eliminate the requirement that the comment delimiters be passed as parameters (or expand the definition of those parameters to include their aspects which have been implicitly specified... but I can not see a good way to do that). I would also include explicit examples for the treatment of character sequences which look like delimiters but are not delimiters because of their position. |
|||
:If my interpretation is acceptable, I could tackle re-writing the task specification. --[[User:Rdm|Rdm]] 18:47, 2 November 2010 (UTC) |
|||