Patrick R. Michaud wrote:
On Mon, Aug 10, 2009 at 06:46:34PM +0100, smuj wrote:
Although I can see some minimal uses for embedded comments, I think in
general the cost/benefit ratio isn't enough to warrant their existence.
I could be wrong of course! :-) I'd like to know if anyone has made much
use of them in their code, and under what circumstances.
I've used embedded comments a number of times (especially in examples)
and found them to be incredibly useful. I'd be sad to see them disappear.
I'd be fine with the ##(embedded comment solution) approach (doubling
the #'s), but it's much less visually appealing to me. I think I'd
prefer to see a doubling of the bracketing chars instead of doubling
the #'s -- the # is visually a "heavy" glyph and I'd prefer
something a bit lighter.
#((embedded comment))
#{{embedded comment}}
Pm
Yep, I agree that #((blah)) is better than ##(blah). It's much easier to
pick out and far more difficult to create by mistake, so it satisfies my
notion of being "purposeful", whilst also lessening the possibility of
"gotchas"! It's also better because it's already valid embedded comment
syntax:
[S02] {For all quoting constructs that use user-selected brackets, you
can open with multiple identical bracket characters, which must be
closed by the same number of closing brackets}
The "special rule" disallowing embedded comments as the first thing on a
line could be done away with, easing the learning curve of those new to
the language, so this seems like a good idea all round -- unless you're
the poor soul who has to change the grammar yet again! ;-)
Cheers,
--
smuj
