Jonathan Lang wrote:
> How about '~#', meaning something along the lines of "string-like
> comment"?  The idea is that the syntax that follows this would conform
> closely to that of string literals (i.e., quotes).  We might even
> consider loosening the restrictions on delimiter characters, allowing
> the full versatility of quoting delimiters, since there'd no longer be
> any danger of confusing this with a line comment.  So:

For the record: if this gets implemented as I'm describing above, I
will personally restrict myself to using bracketing characters as the
delimiters.  Non-bracketing delimiters have issues that, as a
programmer, I don't want to have to deal with: e.g., if I were to use
'~#/ ... /' to comment out a block of code, I'd have to be very sure
that said code doesn't do any division.  This is still a problem with
brackets, but less so - especially with the ability to double up (or
more) on the brackets.  E.g., '~#[[ ... ]]' pretty much guarantees
that I'll comment out exactly what I want to comment out on the first

Oh, and I just realized: '~#( ... )' looks a bit like an
ascii-graphics thought bubble, as used in old text-based MUXs.  If
'~#' gets nixed, perhaps 'oO' would be a viable alternative?

  $x = oO(here's a comment) 5;

Jonathan "Dataweaver" Lang

Reply via email to