From: Sean Chittenden <sean-ruby-talk@...>
Date: 2001-07-05T14:43:51+09:00
Subject: [ruby-talk:17276] Re: /* */ comments


--y0ulUmNC+osPPQO6
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

> |	Given some of the other comments, I have yet to see a real
> |reason not to have this committed.  Any thoughts Matz?
>=20
> Only if Guy Hurst's concern (which I have too) in [ruby-talk:17257]
> would meet concensus.  I think it's not too hard problem.

	I've been thinking about this too.  I think what we need to do
is setup some kind of order or priority for comments.  ;~)  Comments are
comments, but they're not necessarily created equal.  How's the
following order sound?

1)  RD directives
2)  Single line and multi-line comments

	With that order, it's possible to have # and /* */ comments in
the documentation (might be useful for some reason).  As for the problem=20
that Guy brought up, yes, this would be an error:

/*
=3Dbegin
what about this?
Am I RD or a comment?
*/
=3Dend # error or not?

	This however, would be valid:

/* Source code comment

=3Dbegin
This is an RD comment
/* another RD comment */
an RD comment
=3Dend # end of rd documentation

still a source code comment
*/


	How's that sound?  -sc

--=20
Sean Chittenden

--y0ulUmNC+osPPQO6
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Comment: Sean Chittenden <sean@chittenden.org>

iEUEARECAAYFAjtD/o0ACgkQn09c7x7d+q0oJgCWM3gpdkKWf4+FGHY/gW05/4Tx
wQCfQNGjTmqozMPmTFGUZD0NwFKjJM0=
=zKt9
-----END PGP SIGNATURE-----

--y0ulUmNC+osPPQO6--