On Thursday, 18 February 2016 at 23:48:44 UTC, Elie Morisse wrote:
> Calypso classes deriving from DMD ones will have to be converted to D […]

This is not necessarily true. You should be able to inherit from an extern(C++) class just fine on the C++ side. Of course, Walter is busy converting various internals to D, but it should be possible to keep the parts you need accessible from C++.

Please make sure let us know if we can do anything on the LDC side to make the transition easier.

 — David

On Sunday, 21 February 2016 at 22:23:10 UTC, Kagamin wrote:
> On Sunday, 21 February 2016 at 17:21:51 UTC, Brad Roberts wrote:
>> Is there anything preventing Calypso from turning into a code and interface generator?  Making it an application that is part of the build rather than a plug in to ldc would make it available to both dmd and gdc users, no?
>
> That's DStep: https://github.com/jacob-carlborg/dstep

I don't think that works for C++, and it's not complete.

On Sun, 21 Feb 2016 09:21:51 -0800, Brad Roberts via Digitalmars-d-announce wrote:

> Making it an application that is part of the build
> rather than a plug in to ldc would make it available to both dmd and gdc
> users, no?

And it would sidestep issues where I run dstep on one platform and try to use the results on another, but some #defines are incorrect for the second platform.

Of course, that's true for any build-time conversion scheme. Running dstep as part of a build would be equivalent.

In terms of practicality, I'd sooner turn to CastXML. It's easier to inspect than clang AST.

On Sunday, 21 February 2016 at 23:30:14 UTC, bachmeier wrote:
> I don't think that works for C++, and it's not complete.

At least it's intended to generate bindings, Calypso does very different thing. So if one wants bindings generation, it would be easier to implement missing functionality in DStep.

On 02/22/2016 01:30 AM, bachmeier wrote:
> On Sunday, 21 February 2016 at 22:23:10 UTC, Kagamin wrote:
>> On Sunday, 21 February 2016 at 17:21:51 UTC, Brad Roberts wrote:
>>> Is there anything preventing Calypso from turning into a code and interface generator?  Making it an application that is part of the build rather than a plug in to ldc would make it available to both dmd and gdc users, no?
>>
>> That's DStep: https://github.com/jacob-carlborg/dstep
> 
> I don't think that works for C++, and it's not complete.

The very reason why Calypso doesn't work with C++ so well is also the reason why you won't be able to generate bindings easily - it calls C++ code directly without creating intermediate D interface in any form.

On Monday, 22 February 2016 at 10:20:35 UTC, Dicebot wrote:

> The very reason why Calypso doesn't work with C++ so well is also the reason why you won't be able to generate bindings easily - it calls C++ code directly without creating intermediate D interface in any form.

I wanted to clarify that it doesn't currently claim to be a tool for creating C++ bindings, so as not to mislead someone trying out the language.

On 02/22/2016 12:20 PM, Dicebot wrote:
> The very reason why Calypso doesn't work with C++ so well is also the reason why you won't be able to generate bindings easily - it calls C++ code directly without creating intermediate D interface in any form.

Typo: "very reason why Calypso DOES work with C++ so well"