Multiline comments?

ruby-talk
1

The first reason is the notation. At least, (* ) and / */
conflicted or didn’t match with Ruby’s syntax. Do you have
any idea?

At first thought I couldn’t think of anything that would conflict with

<<< comment >>>

or

← comment →

neat. never thought about that too…

also maybe:

<== comment ==>
#-- comment --#
#== comment ==#

Bernhard

kind regards -botp

···

Bernhard Weitzhofer [mailto:weitzhof@in.tum.de] wrote:

nobu.nokada@softhome.net wrote:

2

Scripsit illa aut ille »Peña, Botp« botp@delmonte-phil.com:

···

Bernhard Weitzhofer [mailto:weitzhof@in.tum.de] wrote:

nobu.nokada@softhome.net wrote:

The first reason is the notation. At least, (* ) and / */
conflicted or didn’t match with Ruby’s syntax. Do you have
any idea?

At first thought I couldn’t think of anything that would conflict with

<<< comment >>>

CVS IIRC. Except <<<<<<<<<<<<<<<< … >>>>>>>>>>>>>>>> is invalid.

3

Hi,

···

At Wed, 18 Jun 2003 15:40:01 +0900, Peña, Botp wrote:

At first thought I couldn’t think of anything that would conflict with

<<< comment >>>

or

← comment →

neat. never thought about that too…

also maybe:

<== comment ==>
#-- comment --#
#== comment ==#

Once I thought like them.

(| this would not conflict |)
(= something looks like face mark =)

Hmmm, (|:/ /:|) never conflict.

–
Nobu Nakada

4

Hope these will be nestable :wink:

(|:/ Top (|:/ Lvl2 /:|)
p ‘catastrophe’
(|:/ Inner /:|)
Top
/:|)
p ‘Free at last’

I’m writing the spec. for a macro now ! ;))

···

nobu.nokada@softhome.net wrote:

(| this would not conflict |)
(= something looks like face mark =)

Hmmm, (|:/ /:|) never conflict.

–
Nobu Nakada

#-----

def foo(*args)
yield unless comment_given? or not respond_to?(:anything, true)
rescue
puts “Sorry, I thought you were a block or an arg”
end

foo (| this would not conflict |) # OK, but visually ambiguous?

#-----

I’m guessing you’re ready to implement m-l-comments as soon
as group takes responsibility for the syntax.

Thanks,

(-:
daz
:slight_smile:

5

Hi,

Hope these will be nestable :wink:
(snipped many matz’s faces /:|)

I haven’t considered about nesting.

def foo(*args)
yield unless comment_given? or not respond_to?(:anything, true)
rescue
puts “Sorry, I thought you were a block or an arg”
end

foo (| this would not conflict |) # OK, but visually ambiguous?

Yes, it’s not nice. What about <| |>?

I’m coming to consider /* */ would be better than the others,
even if it isn’t best.

I’m guessing you’re ready to implement m-l-comments as soon
as group takes responsibility for the syntax.

No, I haven’t started it yet, but implementation is easy, no
problem.

···

At Sat, 21 Jun 2003 17:21:12 +0900, daz wrote:

–
Nobu Nakada