Re: Mono-D v0.4.8

2013-01-16 Thread alex 

On Wednesday, 16 January 2013 at 07:13:01 UTC, timotheecour wrote:

and another bug:
(I've updated to the correct stable version as per your 
instructions, since my last post included). Not sure how to 
reproduce this bug but it just happened after switching back to 
MD (i'm on OSX):


A fatal error has occurred

Details of this error have been automatically sent to Xamarin 
for analysis. MonoDevelop will now close.


System.ArgumentOutOfRangeException: Argument is out of range.
  at MonoDevelop.D.Formatting.Indentation.IndentStack.Push 
(Inside inside, Byte keyword, Int32 lineNr, Int32 nSpaces) 
[0x0] in filename unknown:0


Next time, please dump the upper-most entry of the stack trace 
only ;)


This is fixed now. It'll be part of the next bug-fix release.

Re: A look at the D programming language by Ferdynand Górski

2013-01-16 Thread Regan Heath 
On Tue, 15 Jan 2013 20:06:05 -, Walter Bright  
newshou...@digitalmars.com wrote:



On 1/15/2013 4:09 AM, bearophile wrote:
One common indentation-related bug is caused by relying on the  
indentation to
understand code, while the curly brace language compiler ignores what  
you were

seeing and only sees the braces. I have seen many cases of delayed code
understanding caused by that. Making the syntax more DRY (this means  
stating the
logical indentation using only one communication channel) helps avoid  
those
mistakes (and reduces the visual noise, further helping code  
readability).


This is the job of a syntax aware editor (and other source code  
formatting tools), not the language. In my not-so-humble opinion.


BTW, I'd like to see a source code formatter for D. Anyone want to step  
up?


In an ideal world the source code would be stored in file on disk in some  
standard format, and displayed in each programmers editor in their own  
preferred format.  It could end all arguments about code formatting, for  
good.


R

--
Using Opera's revolutionary email client: http://www.opera.com/mail/