Extensive update of Ddoc, www.digitalmars.com/d/ddoc.html

http://www.digitalmars.com/d/changelog.html

On Sat, 24 Sep 2005 20:43:51 -0400, Walter Bright <newshound@digitalmars.com> wrote:

> Extensive update of Ddoc, www.digitalmars.com/d/ddoc.html
>
> http://www.digitalmars.com/d/changelog.html
>

DMD version number is goofed up all over the place.

Skimming http://www.digitalmars.com/d/ddoc.html again I noticed it says "See_Also: List of other symbols and URL's to related items." and uses "References:" in the code sample.

Walter Bright wrote:
> Extensive update of Ddoc, www.digitalmars.com/d/ddoc.html
> 
> http://www.digitalmars.com/d/changelog.html
> 
> 

Ummm ... 0.133 - right?  The Change Log also says 0.132 but links to 0.133.

"Rod Haper" <rhaper@houston.rr.com> wrote in message news:dh5184$13gv$1@digitaldaemon.com...
> Ummm ... 0.133 - right?

Yes. Fixed.

In article <dh4s2l$vhb$1@digitaldaemon.com>, Walter Bright says...
>
>Extensive update of Ddoc, www.digitalmars.com/d/ddoc.html
>
>http://www.digitalmars.com/d/changelog.html
>

Walter, these are some really great improvements! <g>

But I do have a couple of minor things I've found thus, far that are bugging me.

# 1) I'd like to keep the 'in' in, and one whitespace after the comma (please)
#   ulong gcf(in ulong ulA, in ulong ulB)
# becomes:
#   ulong gcf(ulong ulA,ulong ulB);

# 2) I would also like for my bool to stay, and not have it replaced with bit
#   bool isprime(ulong ulz)
# becomes:
#   bit isprime(ulong ulz);

# 3) And lastly, it seems that any string that matchs the module name, in
#    this case "mathext" gets changed to having two leading spaces and
#    the whole string then underlined.
#
#  "C:\dmd>bin\dmd mathext.d -debug=mathext -unittest"
# becomes:
#  "C:\dmd>bin\dmd __mathext.d -debug=__mathext -unittest"

Thanks for the work you've done so far!

David L.

-------------------------------------------------------------------
"Dare to reach for the Stars...Dare to Dream, Build, and Achieve!"
-------------------------------------------------------------------

MKoD: http://spottedtiger.tripod.com/D_Language/D_Main_XP.html

Can you please alter DMD to use both sc.ini file *and* a user defined .ini file (maybe site_sc.ini) such that the definitions in the user file override the ones in sc.ini. That way, whenever you distribute a new DMD you won't wipe out my changes to sc.ini.

-- 
Derek Parnell
Melbourne, Australia
25/09/2005 4:31:34 PM

"Derek Parnell" <derek@psych.ward> wrote in message news:18dquf8vcj3pn$.16w7fqn2hhp6o.dlg@40tude.net...
> Can you please alter DMD to use both sc.ini file *and* a user defined .ini file (maybe site_sc.ini) such that the definitions in the user file override the ones in sc.ini. That way, whenever you distribute a new DMD you won't wipe out my changes to sc.ini.

Mark yours as read-only, and it should survive.

On Sat, 24 Sep 2005 17:43:51 -0700, Walter Bright wrote:

> Extensive update of Ddoc, www.digitalmars.com/d/ddoc.html
> 
> http://www.digitalmars.com/d/changelog.html

(1) There is something wrong with the .ddoc files. They seem to be completely ignored. I had to rename manual.ddoc to manual.d to get anything at all with this command line ...

   dmd -D -o- config.ddoc manual.ddoc

(2) I don't get anything generated if the file does not contain a module statement. I was hoping to have .ddoc files that only contain documentation comments. These would be used to create End User manuals rather than documentation for developers.

(3) This ...

  $(D_CODE
      $(B pragma)( $(I name) );
      $(B pragma)( $(I name) , $(I option) [ $(I option) ] );
  )

produced this output ...

<pre class="d_code">
      <b> pragma </b>
( <i> name </i>
 );
      <b> pragma </b>
( <i> name </i>
 , <i> option </i>
 [ <i> option </i>
 ] );
</pre>

So it seems that a lot of line breaks were inserted by DMD.

(4) I want to have unmatched parenthesis inside a macro invocation. May I suggest that macro invocation can be kicked off by any sort of brackets. For example ...

   $(B)
   ${B}
   $[B]
   $<B>

all invoke the B macro. Then I could do this ...

    $[B pragma(] name $B[);]

(5) This ...

Example 1
 $(D_CODE
      // This app needs the MyGUI.lib library to be used.
      version(build) { pragma(link, MyGUI); }
 )

 Example 2
 $(D_CODE

      // This app needs the a DB library and TCP library to be used.
      version(build) { pragma(link, EuDB, TCP4Win); }
 )

produced this output ...

Example 1
<pre class="d_code">
      // This app needs the MyGUI.lib library to be used.
      version(build) { pragma(link, MyGUI); }
</pre>

</p>
<p>
Example 2
<pre class="d_code">
</pre>

<p>
      // This app needs the a DB library and TCP library to be used.
      version(build) { pragma(link, EuDB, TCP4Win); }
</p>


-- 
Derek Parnell
Melbourne, Australia
25/09/2005 4:51:58 PM

On Sat, 24 Sep 2005 23:50:00 -0700, Walter Bright wrote:

> "Derek Parnell" <derek@psych.ward> wrote in message news:18dquf8vcj3pn$.16w7fqn2hhp6o.dlg@40tude.net...
>> Can you please alter DMD to use both sc.ini file *and* a user defined .ini file (maybe site_sc.ini) such that the definitions in the user file override the ones in sc.ini. That way, whenever you distribute a new DMD you won't wipe out my changes to sc.ini.
> 
> Mark yours as read-only, and it should survive.

But then I don't get any new things that you might have created in DMD's sc.ini file.

-- 
Derek Parnell
Melbourne, Australia
25/09/2005 5:23:34 PM

In article <18dquf8vcj3pn$.16w7fqn2hhp6o.dlg@40tude.net>, Derek Parnell says...
>
>Can you please alter DMD to use both sc.ini file *and* a user defined .ini file (maybe site_sc.ini) such that the definitions in the user file override the ones in sc.ini. That way, whenever you distribute a new DMD you won't wipe out my changes to sc.ini.

Or if sc.ini were renamed to sc.ini.sample, and it was up to the user set up the settings if they deviate from the default sc.ini entries. That might be another solution.

I hate it when I set up a custom sc.ini, then it gets overwritten when installing a new version. I've started manually telling 7-zip (the zip program that I use) to not overwrite that file, but it'd be easier in sc.ini was the first entry in the archive. Once I get past sc.ini, I get to just click "Yes to all" (or whatever it is).

jcc7