This is a side effect of what I've come to believe is intended behavior. Khaled has stated before that you should not be mixing comments within commands.

To explain whats happening: when used with a pipe it treats everything from the block-comment opening to the end-of-line as a comment but ends the comment at the EOL. If I had to wager a guess, I'd say that internally the same handler used for a line comment(;) is invoked when a block-comment within a set of piped commands is encountered



As an aside, here's my own notes on block comments:

Code:
Valid:
  /* comment
  */
 
Multi-line with trailing text
Unorthodoxed; 'text' is considered part of comment
  /* comment
  */ text
 
Multi-line with trailing text after pipe
Unorthodoxed; '| text' is considered part of comment
  /* comment
  */ | text
 
Proceeded by a pipe
Unorthodoxed: Starts the block comment but terminates at EOL
  command | /* comment

Single line
Invalid: Doesn't terminate the comment
  /* comment */
 
Leading text with whitespace
Invalid: Doesn't terminate the comment
  /* comment
  text */
 
Leading text without whitespace
Invalid: Doesn't terminate the comment
  /* comment
  text*/
 
Proceeded by command
Invalid: Not recognized as a comment
  command /* comment
  */

Last edited by FroggieDaFrog; 26/05/18 12:43 AM.