"Jarrett Billingsley" <kb3ctd2@yahoo.com> wrote in message news:dimi9f$2ue1$1@digitaldaemon.com...
> "Walter Bright" <newshound@digitalmars.com> wrote in message news:dimcq2$2laq$1@digitaldaemon.com...
> > There isn't an obvious way to control that. The declaration text is
> > actually
> > generated not from the source, but from the symbol table.
>
> So the semicolons are part of the symbols?  That seems odd..

Not what I meant. I meant the text is generated from the symbol table information (you can see that in the dmd front end source). There is no obvious place in it to control the appearance of a semicolon.


> > Try redefining the DDOC_XXXX macros.
> If you mean the DDOC_MEMBERS section, I have.  However, the same macro applies to members of modules _and_ members of classes/structs.  I'd like
to
> know how to (if at all possible) use one macro for the module-level
members,
> and another for class/struct members.

Ok, you're right. It uses the same scheme for all "members of an enclosing symbol", and that includes modules, structs, classes, enums, templates, etc. But does there need to be a distinction?


> > Redefine the D_XXXX macros, which are by default set to:
> >
> > D_COMMENT = $(GREEN $0)
> > D_STRING  = $(RED $0)
> > D_KEYWORD = $(BLUE $0)
> > D_PSYMBOL = $(U $0)
> > D_PARAM   = $(I $0)
>
> Might want to document those; the Doc Doc (hehe) doesn't mention them at
> all.

It does (perhaps you're looking at an older version):

Highlighting of D code is performed by the following macros:
  D Code Formatting Macros D_COMMENT  Highlighting of comments
      D_STRING  Highlighting of string literals
      D_KEYWORD  Highlighting of D keywords
      D_PSYMBOL  Highlighting of current declaration name
      D_PARAM  Highlighting of current function declaration parameters

"Walter Bright" <newshound@digitalmars.com> wrote in message news:dinu23$2j6g$2@digitaldaemon.com...
> Not what I meant. I meant the text is generated from the symbol table information (you can see that in the dmd front end source). There is no obvious place in it to control the appearance of a semicolon.

Still not understanding what you mean, and the frontend is more than a mess. But I'll take your word.

> Ok, you're right. It uses the same scheme for all "members of an enclosing
> symbol", and that includes modules, structs, classes, enums, templates,
> etc.
> But does there need to be a distinction?

Because usually I don't want module-level members styled the same way as class or struct-level members.

> It does (perhaps you're looking at an older version):

Ooh, then there's a problem with the 0.135 archive - it has the 0.134 docs. Just checked the ZIP, looked at the DDoc doc and the changelog, and it's 0.134.