Jump to page: 1 2 3
Thread overview
LDC
Sep 05, 2012
Russel Winder
Sep 05, 2012
Russel Winder
Sep 05, 2012
Russel Winder
Sep 05, 2012
Russel Winder
Sep 13, 2012
Rob T
Sep 14, 2012
Russel Winder
Sep 05, 2012
angel
Sep 05, 2012
Piotr Szturmaj
Sep 05, 2012
Jacob Carlborg
Sep 05, 2012
Nick Sabalausky
Sep 06, 2012
Jacob Carlborg
Sep 05, 2012
Adam D. Ruppe
Sep 06, 2012
Piotr Szturmaj
Sep 13, 2012
Don Clugston
Sep 13, 2012
Jacob Carlborg
Sep 13, 2012
Sean Kelly
Sep 14, 2012
Jacob Carlborg
Sep 14, 2012
Russel Winder
Sep 14, 2012
Daniel Kozak
September 05, 2012
Is there any likelihood of an LDC that is D v2 in the near future. At least on Debian LDC is v1.056.

Thanks.

-- 
Russel. ============================================================================= Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder@ekiga.net 41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel@winder.org.uk London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder


September 05, 2012
On 05-09-2012 14:11, Russel Winder wrote:
> Is there any likelihood of an LDC that is D v2 in the near future. At
> least on Debian LDC is v1.056.
>
> Thanks.
>

I don't know who packages LDC in Debian, but LDC has supported D 2.0 for years.

http://www.github.com/ldc-developers/ldc

-- 
Alex Rønne Petersen
alex@lycus.org
http://lycus.org
September 05, 2012
Check out LDC web-page ...
In github we see they're up to date - merging 2.060
September 05, 2012
On Wed, 2012-09-05 at 14:18 +0200, Alex Rønne Petersen wrote: […]
> 
> I don't know who packages LDC in Debian, but LDC has supported D 2.0 for years.
> 
> http://www.github.com/ldc-developers/ldc

Well I think it will have to be accepted that the entire Debian and Ubuntu world have no knowledge of this. The LDC developers probably need to establish a relationship with whoever the listed Debian packager is.

-- 
Russel. ============================================================================= Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder@ekiga.net 41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel@winder.org.uk London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder


September 05, 2012
angel wrote:
> Check out LDC web-page ...
> In github we see they're up to date - merging 2.060

What's the status of SEH on Windows?
September 05, 2012
On Wed, 2012-09-05 at 13:30 +0100, Russel Winder wrote:
> On Wed, 2012-09-05 at 14:18 +0200, Alex Rønne Petersen wrote: […]
> > 
> > I don't know who packages LDC in Debian, but LDC has supported D 2.0 for years.
> > 
> > http://www.github.com/ldc-developers/ldc
> 
> Well I think it will have to be accepted that the entire Debian and Ubuntu world have no knowledge of this. The LDC developers probably need to establish a relationship with whoever the listed Debian packager is.

I had a quick look, and I surmise that the LDC folk switched from Mercurial to Git but didn't communicate with the Debian packager that this was going to happen.  Since the Mercurial repository hasn't changes in the last two years, neither has the Debian package.  The ldc package got ejected from Testing so will not be in the next Debian release.

Can I suggest that the LDC developers make a release from GitHub and communicate with Arthur Loiret who is listed as the packager so as to get a new ldc package into Experimental and thence Unstable after the freeze is over?

I'll post a bug report on the LDC GitHub site.

-- 
Russel. ============================================================================= Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder@ekiga.net 41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel@winder.org.uk London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder


September 05, 2012
It appears that the LDC website is in need of an overhaul.  Two "highlights": apparently 0.9.2 is the most up-to-date release from over two years ago; and to get source you should clone the Mercurial repository from BitBucket. Strange instructions for a project now hosted on GitHub.

I now see why Debian is so out of date.

-- 
Russel. ============================================================================= Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder@ekiga.net 41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel@winder.org.uk London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder


September 05, 2012
On 2012-09-05 14:32, Piotr Szturmaj wrote:
> angel wrote:
>> Check out LDC web-page ...
>> In github we see they're up to date - merging 2.060
>
> What's the status of SEH on Windows?

It's not looking good, at least not for 32bit. Borland has some kind of patent on something related to SEH. Due to this, the LLVM/Clang developers won't implement SEH for Windows.

BTW, how does DMD handle this. Does it use its own, non-compatible implementation, or is the technology licensed?

http://www.google.com/patents/about?id=21MgAAAAEBAJ&dq=5,628,016

-- 
/Jacob Carlborg
September 05, 2012
On Wed, 05 Sep 2012 20:12:29 +0200
Jacob Carlborg <doob@me.com> wrote:

> On 2012-09-05 14:32, Piotr Szturmaj wrote:
> > angel wrote:
> >> Check out LDC web-page ...
> >> In github we see they're up to date - merging 2.060
> >
> > What's the status of SEH on Windows?
> 
> It's not looking good, at least not for 32bit. Borland has some kind of patent on something related to SEH. Due to this, the LLVM/Clang developers won't implement SEH for Windows.
> 

Meh, it's not physically *possible* to write software that doesn't infringe on some software patent or another. If they're worried about infringing on some patent, they may as well just stop writing code altogether.

> BTW, how does DMD handle this. Does it use its own, non-compatible implementation, or is the technology licensed?
> 
> http://www.google.com/patents/about?id=21MgAAAAEBAJ&dq=5,628,016
> 

I've wondered the same thing.

September 05, 2012
On Wednesday, 5 September 2012 at 18:11:58 UTC, Jacob Carlborg wrote:
> BTW, how does DMD handle this. Does it use its own, non-compatible implementation, or is the technology licensed?

My guess is that Digital Mars probably inherited Symantec's license.

(This is pure speculation on my part, I don't actually know, but
it'd make sense if it is part of the proprietary backend.)
« First   ‹ Prev
1 2 3