View mode: basic / threaded / horizontal-split · Log in · Help
January 30, 2005
Re: Non UTF characters in comments
> Ideally, the HTML used should be made to be valid XHTML as well...

Oh, dreams, dreams... this famous XHTML will never be a "lingua franca" as 
is HTML.
First browser which will enforce showing *only valid* or even only 
well-formed docs will die for the market for many reasons.

Even XHTML standard say that UA (user agent - browser) should try to show 
patrial content.
Strictly speaking, partial content of XML doc is not well formed XML thus 
invalid.

So browsers will show invalid XHTML anyway. So there will not be a strong 
motivation to use valid XHTML,
so XHTML will loose its 'X' and become just HTML v.5,6, etc....

And I am silent yet about CSS grammar where whitespace is an operator with 
different meaning in different places.... Parsing nightmare.
I love this game...

What kind of grammar D uses, is it context free, BTW?

Andrew Fedoniouk.
http://terrainformatica.com
January 30, 2005
Re: Non UTF characters in comments
On 2005-01-29 08:57:23 -0600, Vathix <vathix@dprogramming.com> said:

> I'm not sure if allowing non UTF characters in comments is such a good  
> idea. It seems to be complicating my parser, and it will probably  
> complicate other things like text/code editors. What is supposed to 
> happen  when a non UTF character is encountered? Should it display a 
> question  mark, display nothing, use the current code page? What if the 
> editor  doesn't know about D's comments?
> I might not have mentioned this, but since D is suppsed to be easily  
> parsed, this might be an issue; a special case.
> - Chris

I don't know what your situation/eviroment is, but you could just try 
piping the sources files through the GNU iconv utility to convert the 
files to whatever encoding you want.
January 30, 2005
Re: Non UTF characters in comments
On Sun, 30 Jan 2005 01:11:47 +0100, Anders F Björklund wrote:

> Andrew Fedoniouk wrote:
> 
>> Preparation for attributed programming I guess. With option to include 
>> binary data inline :)
> 
> :-)
> 
> No, it's a bug. D source code is supposed to be valid UTF-8/16/32.
> 
> Ideally, the HTML used should be made to be valid XHTML as well...
> 
> --anders

One could argue that comments are not actual D source code ;-) 

Consider: does the compiler needs the comments to create the application?
If the comments are not for the compiler, then why should it care what's in
the comments?

-- 
Derek
Melbourne, Australia
January 30, 2005
Re: Non UTF characters in comments
Andrew Fedoniouk wrote:

> Oh, dreams, dreams... this famous XHTML will never be a "lingua franca" as 
> is HTML.

XHTML *is* both HTML and XML at once, which is why it is so useful...
Just as UTF-8 is both ASCII and Unicode at once, best of both worlds.

> First browser which will enforce showing *only valid* or even only 
> well-formed docs will die for the market for many reasons.

Just because certain browsers display it, is no reason for nonvalid 
markup. And it's easy to verify too, using http://validator.w3.org/ ?

--anders
January 30, 2005
Re: Non UTF characters in comments
Derek wrote:

> One could argue that comments are not actual D source code ;-) 
> Consider: does the compiler needs the comments to create the application?

The source code is not just for the compiler. (I meant "compiler input")

> If the comments are not for the compiler, then why should it care what's in
> the comments?

It makes other stuff like parsers easier, if all .d files are valid UTF.

--anders
Next ›   Last »
1 2 3
Top | Discussion index | About this forum | D home