Removing D embedded in HTML feature

Hans W. Uhlig huhlig at clickconsulting.com
Thu Apr 10 21:34:26 PDT 2008


> Although I keep an eye on these newsgroups and I think D looks nice, I'm 
> not currently using it. So I wouldn't want to vote on the HTML thing. 
> But I agree about code editors.
> 
> I'm kind of surprised, software as gotten to the advanced level it has 
> over the past 20 years or so, and we're still writing source code in 
> ASCII text files. I'm using Visual Studio 2005/2008 to do C++ and C# and 
> it's a great achievement. But we're still using ASCII text files.
> For years I've wanted to draw block diagrams and flow charts right in 
> the code to document what's going on. How great would it be if you could 
> use Microsoft Word to write code with and also draw your diagrams 
> alongside? You could use bold and italics formatting to emphasize 
> important code. Change the size of text, add tables, etc. The compiler 
> doesn't have to understand MS-Word format. Rather, the editor (or some 
> other utility) could just export the ASCII for the compiler's 
> consumption. Perhaps better, create a standard file format for code that 
> can handle graphics and other documentation. Then to avoid the step of 
> exporting the raw ASCII, you can have the file format store the actual 
> code in a separate section that's easy for compilers to find. Then 
> compilers can navigate to that section of the file and ignore everything 
> else. I don't think it's too much to expect standards for source code 
> files, given that standardization seems to have moved along for things 
> like the C++ library and C++98 and 0x. </rant>
> 
> Jim Hewes

I would hate doing this, often times I end up coding over a putty 
terminal on a remote Unix machine. I wouldn't want to fire up a copy of 
X just to edit my file. My coding is done on a remote machine from an 
eeePC, I can do it on nearly anything from anywhere and not worry about 
anything. Perhaps moving to Unicode might be appropriate for source 
files but integrating a binary format into source code is an awful idea.
I agree some form of more complicated method might be appropriate, 
perhaps an xml format for representing UML or similar as a comment 
format would work. Then again this can already be done with normal 
commenting.



More information about the Digitalmars-d mailing list