From: Matthew Kerwin Date: 2017-05-07T08:45:31+10:00 Subject: [ruby-core:81014] Re: [Ruby trunk Feature#13518] Indented multiline comments --===============0300757588== Content-Type: multipart/alternative; boundary=001a114413f277895d054ee2c394 --001a114413f277895d054ee2c394 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 7 May 2017 at 08:13, wrote: > Issue #13518 has been updated by tscheingeld (Terry Scheingeld). > > > duerst (Martin D=C3=BCrst) wrote: > > `=3Dbegin`/`=3Dend` are rare, and it's better to make them stick out. > > I would make the case that `=3Dbegin`/`=3Dend` is rare because it can't b= e > indented. Multiline comments are very handy. It makes syntax highlighting > much cleaner for embedded content (in my case, documentation) if every li= ne > doesn't have to start with a comment from the outer language. > > ---------------------------------------- > Feature #13518: Indented multiline comments > https://bugs.ruby-lang.org/issues/13518#change-64677 > > * Author: tscheingeld (Terry Scheingeld) > * Status: Open > * Priority: Normal > * Assignee: > * Target version: > ---------------------------------------- > I'd like to submit the idea that multiline comments could be indented. > That is, `=3Dbegin` and `=3Dend` do not have to start at column zero. Tha= t > would allow for more flexibility in documenting and commenting code. > =E2=80=8BDoes anybody write actual POD in their =3Dbegin/=3Dend blocks? Personally, never use them to disable code because to my (Perl programmer's) eye they're strictly for documentation. And I don't use them for that because RDoc does it differently. Cheers --=20 Matthew Kerwin http://matthew.kerwin.net.au/ --001a114413f277895d054ee2c394 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On 7 May 2017 at 08:13, <tscheingeld32@gmail.com&= gt; wrote:
Issue #13518 has been u= pdated by tscheingeld (Terry Scheingeld).


duerst (Martin D=C3=BCrst) wrote:
> `=3Dbegin`/`=3Dend` are rare, and it's better to make them stick o= ut.

I would make the case that `=3Dbegin`/`=3Dend` is rare because it ca= n't be indented. Multiline comments are very handy. It makes syntax hig= hlighting much cleaner for embedded content (in my case, documentation) if = every line doesn't have to start with a comment from the outer language= .

----------------------------------------
Feature #13518: Indented multiline comments
https://bugs.ruby-lang.org/issues/13= 518#change-64677

* Author: tscheingeld (Terry Scheingeld)
* Status: Open
* Priority: Normal
* Assignee:
* Target version:
----------------------------------------
I'd like to submit the idea that multiline comments could be indented. = That is, `=3Dbegin` and `=3Dend` do not have to start at column zero. That = would allow for more flexibility in documenting and commenting code.

= =E2=80=8BDoes anybody write actual POD in their =3Dbegin/=3Dend blocks?

Personally, never use them to disable code be= cause to my (Perl programmer's) eye they're strictly for documentat= ion.=C2=A0 And I don't use them for that because RDoc does it different= ly.

Cheers
--
=C2=A0 Matt= hew Kerwin
=C2=A0 http://matthew.kerwin.net.au/
--001a114413f277895d054ee2c394-- --===============0300757588== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Unsubscribe: --===============0300757588==--