This is to fix the spell corrector speed problems and several forward reference bugs.

http://www.digitalmars.com/d/1.0/changelog.html
http://ftp.digitalmars.com/dmd.1.061.zip


http://www.digitalmars.com/d/2.0/changelog.html
http://ftp.digitalmars.com/dmd.2.046.zip

Walter Bright wrote:
> This is to fix the spell corrector speed problems and several forward reference bugs.
> 
> http://www.digitalmars.com/d/1.0/changelog.html
> http://ftp.digitalmars.com/dmd.1.061.zip
> 
> 
> http://www.digitalmars.com/d/2.0/changelog.html
> http://ftp.digitalmars.com/dmd.2.046.zip

Add hints for missing import declarations.

What does that mean?

Ary Borenszweig wrote:
> Walter Bright wrote:
>> This is to fix the spell corrector speed problems and several forward reference bugs.
>>
>> http://www.digitalmars.com/d/1.0/changelog.html
>> http://ftp.digitalmars.com/dmd.1.061.zip
>>
>>
>> http://www.digitalmars.com/d/2.0/changelog.html
>> http://ftp.digitalmars.com/dmd.2.046.zip
> 
> Add hints for missing import declarations.
> 
> What does that mean?

Write the following program:

-------------------
void main()
{
    writeln("hello world!");
}
-------------------

compile it and see what happens. I think it'll be clear!

This release seems to work, thank you.

>Bugzilla 1001: print stack trace (in debug mode) when program die<

Can you or someone else show me an example of how to activate stack tracing?

For example on Windows I have written this small program:

import std.c.stdlib: atoi;
void main() {
    int x = atoi("0.0");
    int y = 10 / x;
}


I compile it with:
dmd -debug test.d

If I run it it prints:
object.Error: Integer Divide by Zero


This other program gives the same output:
import std.c.stdlib: atoi;
import core.runtime;
void main() {
    Runtime.traceHandler = &defaultTraceHandler;
    int x = atoi("0.0");
    int y = 10 / x;
}


Is this a Linux feature only for now, as Sean says in bug 1001? If so, then the changelog can specify it's a linux thing only.

Bye,
bearophile

Walter Bright, el 14 de mayo a las 14:42 me escribiste:
> Ary Borenszweig wrote:
> >Walter Bright wrote:
> >>This is to fix the spell corrector speed problems and several forward reference bugs.
> >>
> >>http://www.digitalmars.com/d/1.0/changelog.html http://ftp.digitalmars.com/dmd.1.061.zip
> >>
> >>
> >>http://www.digitalmars.com/d/2.0/changelog.html http://ftp.digitalmars.com/dmd.2.046.zip
> >
> >Add hints for missing import declarations.
> >
> >What does that mean?
> 
> Write the following program:
> 
> -------------------
> void main()
> {
>     writeln("hello world!");
> }
> -------------------
> 
> compile it and see what happens. I think it'll be clear!

I saw the patches, and having all hardcoded in the compiler doesn't seems like a good idea =/

-- 
Leandro Lucarella (AKA luca)                     http://llucax.com.ar/
----------------------------------------------------------------------
GPG Key: 5F5A8D05 (F8CD F9A7 BF00 5431 4145  104C 949E BFB6 5F5A 8D05)
----------------------------------------------------------------------
¿Cómo estais? ¿Cómo os senteis hoy 29 del membre de 1961 día en que
conmemoreramos la nonésima setima nebulización del martir Peperino
Pómoro junto al Rolo Puente en la ciudad de Jadad?
	-- Peperino Pómoro

Leandro Lucarella wrote:
> I saw the patches, and having all hardcoded in the compiler doesn't seems
> like a good idea =/

I know the hardcoding is probably not the best, but I wanted to try it out to see if it was a good feature before committing a lot of work to it.

The alternative is to use some sort of configuration file for it. The problem, though, is that the hints are for newbies, and newbies probably aren't going to get a configuration file properly set up, especially if there are multiple such files.

Walter Bright wrote:
> Leandro Lucarella wrote:
>> I saw the patches, and having all hardcoded in the compiler doesn't seems
>> like a good idea =/
> 
> I know the hardcoding is probably not the best, but I wanted to try it out to see if it was a good feature before committing a lot of work to it.
> 
> The alternative is to use some sort of configuration file for it. The problem, though, is that the hints are for newbies, and newbies probably aren't going to get a configuration file properly set up, especially if there are multiple such files.

I think the only purpose of such a feature is to increase the chance that a newbie's "hello world" compiles successfully. The importance of that can't be underestimated, I think. First impressions matter.

Don wrote:
> Walter Bright wrote:
>> Leandro Lucarella wrote:
>>> I saw the patches, and having all hardcoded in the compiler doesn't seems
>>> like a good idea =/
>>
>> I know the hardcoding is probably not the best, but I wanted to try it out to see if it was a good feature before committing a lot of work to it.
>>
>> The alternative is to use some sort of configuration file for it. The problem, though, is that the hints are for newbies, and newbies probably aren't going to get a configuration file properly set up, especially if there are multiple such files.
> 
> I think the only purpose of such a feature is to increase the chance that a newbie's "hello world" compiles successfully. The importance of that can't be underestimated, I think. First impressions matter.

Yes, or at least have a to-the-point error message rather than just an undefined identifier.

It's amazing how much information we take for granted. For example, I've been trying to use Apple's xcode system. I find it hard to do the most trivial things, like trying to figure out how to just start the thing.

Apple's web site isn't much better, it's got to be the most hard to read site I've ever encountered. The text is a faint grey on white, of all things, and the font is so poorly rendered my eyes turn red and painful after a while reading it. I have to actually select the text in order to read it. I find this astonishing, am I doing something wrong?

It won't render at all in Explorer.

The D web site is rather pedestrian, but at least it's easy on the eyes.

On 5/15/10 11:00, Walter Bright wrote:
> Don wrote:
>> Walter Bright wrote:
>>> Leandro Lucarella wrote:
>>>> I saw the patches, and having all hardcoded in the compiler doesn't
>>>> seems
>>>> like a good idea =/
>>>
>>> I know the hardcoding is probably not the best, but I wanted to try
>>> it out to see if it was a good feature before committing a lot of
>>> work to it.
>>>
>>> The alternative is to use some sort of configuration file for it. The
>>> problem, though, is that the hints are for newbies, and newbies
>>> probably aren't going to get a configuration file properly set up,
>>> especially if there are multiple such files.
>>
>> I think the only purpose of such a feature is to increase the chance
>> that a newbie's "hello world" compiles successfully. The importance of
>> that can't be underestimated, I think. First impressions matter.
>
> Yes, or at least have a to-the-point error message rather than just an
> undefined identifier.
>
> It's amazing how much information we take for granted. For example, I've
> been trying to use Apple's xcode system. I find it hard to do the most
> trivial things, like trying to figure out how to just start the thing.
>
> Apple's web site isn't much better, it's got to be the most hard to read
> site I've ever encountered. The text is a faint grey on white, of all
> things, and the font is so poorly rendered my eyes turn red and painful
> after a while reading it. I have to actually select the text in order to
> read it. I find this astonishing, am I doing something wrong?

Looking at Apple's developer site and the API reference, for me the body of the text is black using firefox, some minor parts are in gray.

> It won't render at all in Explorer.
>
> The D web site is rather pedestrian, but at least it's easy on the eyes.

On 5/15/10 05:46, Walter Bright wrote:
> Leandro Lucarella wrote:
>> I saw the patches, and having all hardcoded in the compiler doesn't seems
>> like a good idea =/
>
> I know the hardcoding is probably not the best, but I wanted to try it
> out to see if it was a good feature before committing a lot of work to it.
>
> The alternative is to use some sort of configuration file for it. The
> problem, though, is that the hints are for newbies, and newbies probably
> aren't going to get a configuration file properly set up, especially if
> there are multiple such files.

How about generating a file with all imports of Phobos, ship the file with the compiler and then read from the file. Something like having a configuration file that is set up to work with everything from Phobos to start with, then the user can add more things if he/she likes to.