On Tue, 06 Oct 2009 21:28:58 -0300, Leandro Lucarella wrote:
Walter Bright, el 6 de octubre a las 12:07 me escribiste:
Robert Clipsham wrote:
Walter Bright wrote:
Then please go ahead and set it up.
What exactly would you like setting up? Currently I'm thinking:
* Automated builds of
Robert Clipsham wrote:
Leandro Lucarella wrote:
Thanks for finally taking this way, Walter =)
http://www.dsource.org/projects/dmd/timeline
Now that DMD is under version control it should be fairly easy for me to
adapt the automated build system used for ldc for dmd. I can set it up
to
Walter Bright wrote:
Jason House wrote:
With small commits to dmd, it should be trivial to know what small
change in dmd caused a user observable change in behavior.
The problem is, one doesn't know if it is a problem with the change or
if it is a problem with the user code. To determine
Don wrote:
I think that'd be fantastic. It'd be helpful if you could at least get
dstress to run after the main releases. The dstress test page from LDC
doesn't seem to operate any more.
http://www.incasoftware.de/~kamm/ldc/tests/index.html
This page gets updated manually by Christian as he
Walter Bright wrote:
Then please go ahead and set it up.
What exactly would you like setting up? Currently I'm thinking:
* Automated builds of dmd 1 and 2
* Automated builds of druntime, phobos and tango
* Automated DStress runs
* Automated dmd test suite runs (if you're willing to provide me
Robert Clipsham wrote:
Walter Bright wrote:
Then please go ahead and set it up.
What exactly would you like setting up? Currently I'm thinking:
* Automated builds of dmd 1 and 2
* Automated builds of druntime, phobos and tango
* Automated DStress runs
* Automated dmd test suite runs (if
Walter Bright Wrote:
It's outlined in the code comments, but it's implemented by making the
contract code a nested function. The overriding function calls those
nested functions of the overridden function(s). In order for this to
work successfully, the 'this' pointer and the stack
Leandro Lucarella wrote:
Thanks for finally taking this way, Walter =)
http://www.dsource.org/projects/dmd/timeline
Now that DMD is under version control it should be fairly easy for me to
adapt the automated build system used for ldc for dmd. I can set it up
to automatically build dmd
Robert Clipsham wrote:
Leandro Lucarella wrote:
Thanks for finally taking this way, Walter =)
http://www.dsource.org/projects/dmd/timeline
Now that DMD is under version control it should be fairly easy for me to
adapt the automated build system used for ldc for dmd. I can set it up
to
Walter Bright Wrote:
Robert Clipsham wrote:
Leandro Lucarella wrote:
Thanks for finally taking this way, Walter =)
http://www.dsource.org/projects/dmd/timeline
Now that DMD is under version control it should be fairly easy for me to
adapt the automated build system used for ldc
Jason House wrote:
Walter Bright Wrote:
Robert Clipsham wrote:
Leandro Lucarella wrote:
Thanks for finally taking this way, Walter =)
http://www.dsource.org/projects/dmd/timeline
Now that DMD is under version control it should be fairly easy
for me to adapt the automated build system used
Andrei Alexandrescu, el 5 de octubre a las 19:17 me escribiste:
Jason House wrote:
Walter Bright Wrote:
Robert Clipsham wrote:
Leandro Lucarella wrote:
Thanks for finally taking this way, Walter =)
http://www.dsource.org/projects/dmd/timeline
Now that DMD is under version control it
Jason House wrote:
With small commits to dmd, it should be trivial to know what small
change in dmd caused a user observable change in behavior.
The problem is, one doesn't know if it is a problem with the change or
if it is a problem with the user code. To determine that requires
working
Hello Walter,
I can set it
up to automatically build dmd after a commit, and run dstress/build
popular projects and libraries
The problem is if some package fails, then I have a large debugging
problem trying to figure out unfamiliar code.
Or it could just inform the owner of the lib and
Walter Bright wrote:
Stewart Gordon wrote:
I'm still none the wiser about why it absolutely has to be done like
this instead of the simpler solution I proposed years ago.
Can you refresh my memory?
Seems straightforward to find to me, but here it is:
Walter Bright wrote:
snip
There are some tricky bits to doing contract inheritance, I hope gdc and
ldc don't have trouble with it.
What tricky bits are those?
Stewart.
Stewart Gordon wrote:
Walter Bright wrote:
snip
There are some tricky bits to doing contract inheritance, I hope gdc
and ldc don't have trouble with it.
What tricky bits are those?
It's outlined in the code comments, but it's implemented by making the
contract code a nested function. The
Walter Bright wrote:
Stewart Gordon wrote:
Walter Bright wrote:
snip
There are some tricky bits to doing contract inheritance, I hope gdc
and ldc don't have trouble with it.
What tricky bits are those?
It's outlined in the code comments, but it's implemented by making the
contract code a
Dejan Lekic wrote:
You guys are doing awesome job with GDC, thank you _VERY MUCH_!
GDC is the only D2 compiler for 64bit architecture...
Actually, there are no D2 compilers for 64 bit. GDC's support for D2 is
very minimal, I don't know how it compares to LDC's, but I'd guess they
were about
Leandro Lucarella wrote:
http://www.dsource.org/projects/dmd/timeline
Thanks Walter.
;)
Now, thanks to the public svn we can track changes easily. This will help
development of gdc too!
Btw today Michael merged dmd 1.035 and i'm close to finish dmd 2.015
See you.
Vincenzo Ampolo wrote:
Now, thanks to the public svn we can track changes easily. This will help
development of gdc too!
I'm glad you guys have picked up gdc.
There are some tricky bits to doing contract inheritance, I hope gdc and
ldc don't have trouble with it.
Thanks for finally taking this way, Walter =)
http://www.dsource.org/projects/dmd/timeline
--
Leandro Lucarella (luca) | Blog colectivo: http://www.mazziblog.com.ar/blog/
GPG Key: 5F5A8D05 (F8CD F9A7 BF00 5431 4145
Leandro Lucarella wrote:
Thanks for finally taking this way, Walter =)
You're welcome. I hadn't done it before because I couldn't figure out a
reasonable way of implementing it.
Walter Bright, el 27 de septiembre a las 13:45 me escribiste:
Leandro Lucarella wrote:
Thanks for finally taking this way, Walter =)
You're welcome. I hadn't done it before because I couldn't figure
out a reasonable way of implementing it.
I don't know if you are talking about DMD being in
24 matches
Mail list logo
