You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
The current comments syntax ending a ccomment either with a newline or a semicolon creates issues when the commented text already contains semicolons which is a very common character to be contained in any text.
Traditionally, the comments were either ending in a newline (e.g. C++ the //, shell the #, BASIC the REM) or multi-line (or part-of-line-short) comments were contained between A COMBINATION of characters (typically C's /* and */) which were deemed by the language creator quite improbable to occur.
And quite right so as this direction has been generally followed by several languages over decades without problems (except the nested comments of C which were not supported anyway).
What made you, Oh I wonder, seek and discover your own way of ending comments "with either a semicolon or a newline"? If you want to provide a way to create a short comment use the directions used by the giants of language authoring (let's say /* short comment*/) rather than invening this new style which breaks all my code as a semicolon (;) is VERY COMMON in Javascript and CSS and has already a meaning in your own Kolon syntax as a statement separator.
Please either reconsider ending comments with a semicolon or provide an alternative comments syntax for the short-comment with a combination of characters wrapping the comment which will not be common within code. If you want my opinion, just stick with the "# to the end of line comment" and keep it simple and succinct.
Thank you
The text was updated successfully, but these errors were encountered:
Hi,
The current comments syntax ending a ccomment either with a newline or a semicolon creates issues when the commented text already contains semicolons which is a very common character to be contained in any text.
Traditionally, the comments were either ending in a newline (e.g. C++ the
//
, shell the#
, BASIC theREM
) or multi-line (or part-of-line-short) comments were contained between A COMBINATION of characters (typically C's/*
and*/
) which were deemed by the language creator quite improbable to occur.And quite right so as this direction has been generally followed by several languages over decades without problems (except the nested comments of C which were not supported anyway).
What made you, Oh I wonder, seek and discover your own way of ending comments "with either a semicolon or a newline"? If you want to provide a way to create a short comment use the directions used by the giants of language authoring (let's say
/* short comment*/
) rather than invening this new style which breaks all my code as a semicolon (;
) is VERY COMMON in Javascript and CSS and has already a meaning in your own Kolon syntax as a statement separator.Please either reconsider ending comments with a semicolon or provide an alternative comments syntax for the short-comment with a combination of characters wrapping the comment which will not be common within code. If you want my opinion, just stick with the "
# to the end of line comment
" and keep it simple and succinct.Thank you
The text was updated successfully, but these errors were encountered: