Ivan Senji wrote:
> Don Clugston wrote:
> 
>> Try compiling this little baby. There's a bug in the code,
>> but the error message is about five megabytes long!
> 
> 
> hm, I don't get it.
> 
> I tried to compile your code:
> 
> build test.d -clean >> output.txt
> 
> and output.txt is 15MB!

Try 'build test.d -clean > output.txt' ;)

Don Clugston schrieb am 2005-11-24:
> Try compiling this little baby. There's a bug in the code,
> but the error message is about five megabytes long!
> Brings Windows to its knees.
>
> If you change the second line to const real val=0x1p90, the error message drops to about 100kb long.
>
> I think we need an error for "Compilation Error limit exceeded". Ideally it would be user-configurable, with a default limit of probably about 100-200 errors.
>
> ---------------
> template a()
> {
>    const real val= 0x1p990;
> }
>
> template half(alias f)
> {
>    const real val = f.val/2;
> }
>
> template c(alias f)
> {
>     static if (f.val > 2.0)  const int val = c!( half!(f) ).val;
> }
>
> const int m = c!(a!()).val;

Added to DStress as http://dstress.kuehne.cn/complex/error_message/error_message_01_A.d http://dstress.kuehne.cn/complex/error_message/error_message_01_B.d http://dstress.kuehne.cn/complex/error_message/error_message_01_C.d

Thomas

Niko Korhonen schrieb am 2005-11-25:
> Georg Wrede wrote:
>> You're too valuable to waste your time "fighting with the computer"!
>> 
>> Unless your D programs do GUI stuff, I'd suggest you do your programming on Linux.

<snip>

> What if I didn't know the 'ulimit' magic word? What if I tried 'man limit', 'man stack', 'man memory' or 'man number of files'?
man -k limit

stack and memory aren't good keywords as they are very frequent.

> Where can I  get a list of man arguments?
man man  ;-)

>> Once the app is final, then compile it on Windows. You'd save hours!
>
> ...after losing years learning all that Unix folklore, that is!

Nobody told you to use AIX *g*

Seriously there are some very advanced IDEs on Windows systems,
but automation/scripting is a pain. How do you replace every "a" by a "b" in
every even line of 100 files? (-> man sed)

How about the keyword "LUG"?
(maybe combined with your town/district/province...)

Thomas

clayasaurus wrote:
> Ivan Senji wrote:
> 
>> Don Clugston wrote:
>>
>>> Try compiling this little baby. There's a bug in the code,
>>> but the error message is about five megabytes long!
>>
>>
>>
>> hm, I don't get it.
>>
>> I tried to compile your code:
>>
>> build test.d -clean >> output.txt
>>
>> and output.txt is 15MB!
> 
> 
> Try 'build test.d -clean > output.txt' ;)

I get the same? Should there be any difference?
Is > != >>?

With DMD   0.140 16.161.964 bytes
With DMD <=0.139 15.143.279 bytes

	

Ivan Senji schrieb am 2005-11-27:
> clayasaurus wrote:
>> Ivan Senji wrote:
>> 
>>> Don Clugston wrote:
>>>
>>>> Try compiling this little baby. There's a bug in the code, but the error message is about five megabytes long!
>>>
>>>
>>>
>>> hm, I don't get it.
>>>
>>> I tried to compile your code:
>>>
>>> build test.d -clean >> output.txt
>>>
>>> and output.txt is 15MB!
>> 
>> 
>> Try 'build test.d -clean > output.txt' ;)
>
> I get the same? Should there be any difference?
> Is > != >>?

">" redirects
">>" appends

Thomas

Thomas Kuehne wrote:
> 
> ">" redirects
> ">>" appends
> 

Thanks, i didn't know that :)

Georg Wrede wrote:
> Niko, I choose to take this as, either a rhetorical barrage of questions, or, ehhhh, the other alternative.

Yep, it was a rhetorical barrage of questions. My main point was that just switching to Linux might not help to save much time at all, or at least that these potential time-savings come after a huge initial investment of learning the 'nix folklore.


-- 
Niko Korhonen
SW Developer

Niko Korhonen wrote:
> Georg Wrede wrote:
> 
>> Niko, I choose to take this as, either a rhetorical barrage of questions, or, ehhhh, the other alternative.
> 
> Yep, it was a rhetorical barrage of questions. My main point was that just switching to Linux might not help to save much time at all, or at least that these potential time-savings come after a huge initial investment of learning the 'nix folklore.

Sigh.

How much Windows or MSDOS do you have to know, if you develop using the command line DMD?

One does not need very much Unix knowledge just to edit and compile. For example, often I don't even bother to fire up the GUI, I just use the console window.

Just about ls, cd, mkdir, rmdir, cat, less, joe, -- can get you a long way. (Which is not more than what one used to learn from a 20 year old MSDOS user's guide.)

If that seems hard, then for that person it really is best to avoid Unix.

Don Clugston wrote:
> Try compiling this little baby. There's a bug in the code,
> but the error message is about five megabytes long!
> Brings Windows to its knees.
> 
> If you change the second line to const real val=0x1p90, the error message drops to about 100kb long.
> 
> I think we need an error for "Compilation Error limit exceeded".
> Ideally it would be user-configurable, with a default limit of probably about 100-200 errors.
> 
> ---------------
> template a()
> {
>   const real val= 0x1p990;
> }
> 
> template half(alias f)
> {
>   const real val = f.val/2;
> }
> 
> template c(alias f)
> {
>    static if (f.val > 2.0)  const int val = c!( half!(f) ).val;
> }
> 
> const int m = c!(a!()).val;
> --------------------

Wow!!! the output I get is ~10 MB, but I didn't get any crashes or anything.
Seems to me like an infinite parsing loop.

Georg Wrede wrote:
> Niko Korhonen wrote:
> 
>> Georg Wrede wrote:
>>
>>> Niko, I choose to take this as, either a rhetorical barrage of questions, or, ehhhh, the other alternative.
>>
>>
>> Yep, it was a rhetorical barrage of questions. My main point was that just switching to Linux might not help to save much time at all, or at least that these potential time-savings come after a huge initial investment of learning the 'nix folklore.
> 
> 
> Sigh.
> 
> How much Windows or MSDOS do you have to know, if you develop using the command line DMD?
> 
> One does not need very much Unix knowledge just to edit and compile. For example, often I don't even bother to fire up the GUI, I just use the console window.
> 
> Just about ls, cd, mkdir, rmdir, cat, less, joe, -- can get you a long way. (Which is not more than what one used to learn from a 20 year old MSDOS user's guide.)
> 
> If that seems hard, then for that person it really is best to avoid Unix.

As the catalyst for the flame war, I should mention that one of my machines is a dual-boot SuSE Linux machine, so I'm not completely ignorant of the UNIX command line. You're right that I should look at doing some D dev in Linux. Unfortunately
(a) the power supply for the PC has died, not yet repaired, so I only have my Windows laptop right now;
(b) I am doing some GUI stuff, and also linking to Windows DLLs. So Linux is not really an option for most of what I'm doing right now.

Since almost all my free time is while commuting, I'm restricted to Windows.