OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

relax-ng message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: RE: [relax-ng] Re: [relax-ng-comment] ## comments in compact syntax


Yes, it just ignores such comments, as in

/***/
/****/
/*****/
/******/
/*******/
/********/
/*********/
/**********/
etc.

I tested this every which way from Tuesday.

Mike

> -----Original Message-----
> From: James Clark [mailto:jjc@jclark.com]
> Sent: Wednesday, September 25, 2002 11:30 PM
> To: Michael Fitzgerald; David Rosenborg;
> relax-ng-comment@lists.oasis-open.org
> Cc: relax-ng@lists.oasis-open.org
> Subject: RE: [relax-ng] Re: [relax-ng-comment] ## comments in compact
> syntax
>
>
> You mean javadoc ignores such a comment?
>
> --On 25 September 2002 22:24 -0700 Michael Fitzgerald <mike@wyeast.net>
> wrote:
>
> > Javadoc doesn't fret over /**********************/. It just
> happily rolls
> > along. -Mike
> >
> >> -----Original Message-----
> >> From: James Clark [mailto:jjc@jclark.com]
> >> Sent: Wednesday, September 25, 2002 8:07 PM
> >> To: David Rosenborg; relax-ng-comment@lists.oasis-open.org
> >> Cc: relax-ng@lists.oasis-open.org
> >> Subject: [relax-ng] Re: [relax-ng-comment] ## comments in
> compact syntax
> >>
> >>
> >> Interesting point.  Does anybody know what javadoc does with
> >>
> >> /**********************/
> >>
> >> or C# with
> >>
> >> ////////////////////////
> >>
> >> ?
> >>
> >> --On 25 September 2002 21:14 +0200 David Rosenborg
> >> <david.rosenborg@pantor.com> wrote:
> >>
> >> >
> >> > I think one common pattern when you comment code is to use comment
> >> > charaters as  dividers of major sections like:
> >> >
> >> ># Some major section follows
> >> >#########################################################
> >> >
> >> > The problem here is that the divider line is treated specially since
> >> > it starts with ##. It is a bit supricing but you can get around
> >> it easily
> >> > by adding an extra space:
> >> >
> >> >
> >> ># Some major section follows
> >> ># #######################################################
> >> >
> >> > I think one solution would be to only recognize ## as a documentation
> >> > comment if it is followed by a non-# character. The disadvantage with
> >> > this is that you will possibly need an extra character of
> lookahead in
> >> > the  parser.
> >> >
> >> > Cheers,
> >> > David
> >> >
> >>
> >>
> >>
> >> ----------------------------------------------------------------
> >> To subscribe or unsubscribe from this elist use the subscription
> >> manager: <http://lists.oasis-open.org/ob/adm.pl>
> >>
> >
> >
> > ----------------------------------------------------------------
> > To subscribe or unsubscribe from this elist use the subscription
> > manager: <http://lists.oasis-open.org/ob/adm.pl>
> >
> >
>
>
>



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC