I've been using it for a month now, and it seems to work. I'm especially interested in the experiences of those on a multicore cpu.

http://ftp.digitalmars.com/Digital_Mars_C++/Patch/beta.zip

Dear Walter,
I have a dual core AMD Athlon and I will test all the test programs you supply with D on this linker.  Then after I get through writing my program I will test it on that linker.
I will try and post here every once and a while to let you know how my experience with the linker goes.

 http://ftp.digitalmars.com/Digital_Mars_C++/Patch/beta.zip

Lester L. Martin The 2nd wrote:
> I have a dual core AMD Athlon and I will test all the test programs you supply with D on this linker.  Then after I get through writing my program I will test it on that linker.
> I will try and post here every once and a while to let you know how my experience with the linker goes.

Thanks.

Walter Bright wrote:
> I've been using it for a month now, and it seems to work. I'm especially interested in the experiences of those on a multicore cpu.
> 
> http://ftp.digitalmars.com/Digital_Mars_C++/Patch/beta.zip

Out of curiosity - what are the improvements over the old one?


Mitja (xs0)

All samples have compiled correctly and ran correctly.
I am going to create a sample program to test the linker.
Walter Bright Wrote:

> Lester L. Martin The 2nd wrote:
> > I have a dual core AMD Athlon and I will test all the test programs you supply with D on this linker.  Then after I get through writing my program I will test it on that linker.
> > I will try and post here every once and a while to let you know how my experience with the linker goes.
> 
> Thanks.

Wait better yet I'll test the dfl samples.

hmm...
Why aren't the libs that came with the old linker recompiled for the new linker or just simply copied over(as I had to do)? Are you working on this? Before release you need to do this because a lot of developers will be wondering how come a library such as dfl that needs gdi32.lib and a couple of other odd libs can't compile.
Well anyway I did successfully get all the dfl examples to compile after copying over all the needed libs.  I look forward to the widespread use of this new linker.

My system is AMD Athlon dual core with DMD 1.010 and link 8.00.1 with DFL and soon to be installed tango.

Love the new linker; thanks for all your work on improving the D developer experience.

Lester

Lester L. Martin The 2nd wrote:
> hmm...
> Why aren't the libs that came with the old linker recompiled for the new linker or just simply copied over(as I had to do)? Are you working on this? Before release you need to do this because a lot of developers will be wondering how come a library such as dfl that needs gdi32.lib and a couple of other odd libs can't compile.
> Well anyway I did successfully get all the dfl examples to compile after copying over all the needed libs.  I look forward to the widespread use of this new linker.
> 
> My system is AMD Athlon dual core with DMD 1.010 and link 8.00.1 with DFL and soon to be installed tango.
> 
> Love the new linker; thanks for all your work on improving the D developer experience.
> 
> Lester

Walter usually releases zip packages so they can be "installed" by just unzipping them over your previous install.  I assume that's what he was expecting you to do in this case too.  If the upgrade doesn't work for some reason, you can go back to the previous version by unzipping the previous version over top of the new version.

--bb

my unzip program is wierd then.  It will first replace the folder(removing files inside) and then it will put the new files inside. I have problems do the install you do and so every time I upgrade to a new D I end up having to reinstall everything after uninstalling every thing.  If that is the way Walter intended it then I need to find a better zip program.

tango does not work good with dfl.  There may be a way to get it to work but I have found none so I will uninstall tango because I use DFL more for GUI programs.  If Tango had a good OO GUI I might consider replacing dfl. HINT HINT!!!!!!!!!!