> Do not the same considerations essentially apply to the well established
> /* */ convention used in C? Well maybe you simply *can't* get the "*/"
> string within a block of C code, but still
Yes, the same problem arises in C. And you _can_ get */ in valid code - as the
closing part of
On 03/09/2017 12:49 AM, Rolf Turner wrote:
On 03/09/17 12:29, Duncan Murdoch wrote:
On 02/09/2017 6:57 PM, Rolf Turner wrote:
On 03/09/17 03:56, William Dunlap via R-help wrote:
Is the reason you want a block comment containing code (as opposed to
arbitrary text) that you want to be able to
On 03/09/17 12:29, Duncan Murdoch wrote:
On 02/09/2017 6:57 PM, Rolf Turner wrote:
On 03/09/17 03:56, William Dunlap via R-help wrote:
Is the reason you want a block comment containing code (as opposed to
arbitrary text) that you want to be able to easily run the commented out
code? If so th
On 02/09/2017 6:57 PM, Rolf Turner wrote:
On 03/09/17 03:56, William Dunlap via R-help wrote:
Is the reason you want a block comment containing code (as opposed to
arbitrary text) that you want to be able to easily run the commented out
code? If so the 'if()' construct has the advantage that yo
On 03/09/17 03:56, William Dunlap via R-help wrote:
Is the reason you want a block comment containing code (as opposed to
arbitrary text) that you want to be able to easily run the commented out
code? If so the 'if()' construct has the advantage that you only need to
change code at the start of
5 matches
Mail list logo
