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
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
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
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
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
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
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
Though fully automatic generation of bindings will be very
difficult because DMD uses semantics deviating from that of C++,
which will require some heuristic analysis.
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?
On 2/21/2016 9:09 AM, Elie Morisse via Digitalmars-d-announce wrote:
On Saturday, 20 February 2016 at 17:34:48 UTC, Nicolas F. wrote:
This is really cool and an interesting project, though I've got one
concern: How will this fit in with the rest of the C++ efforts done
upstream? (...) or is the
On Saturday, 20 February 2016 at 17:34:48 UTC, Nicolas F. wrote:
This is really cool and an interesting project, though I've got
one concern: How will this fit in with the rest of the C++
efforts done upstream? (...) or is the goal to upstream these
changes and make them an officially
This is really cool and an interesting project, though I've got one
concern: How will this fit in with the rest of the C++ efforts done
upstream? As I see it the goal here is to spearhead a working Qt <-> D
interaction, but how would this be used in production? Would Calypso
simply be run to
On Thursday, 18 February 2016 at 03:07:22 UTC, Ali Çehreli wrote:
Congratulations! Any project that can get rid of moc is a big
achievement. :) Folks at CopperSpice had done the same in C++
with their Qt replacement:
http://www.copperspice.com/
Ali
Nice! I've never heard of them,
On Thursday, 18 February 2016 at 02:47:37 UTC, Elie Morisse wrote:
Hi all,
I now have a working D replacement for moc:
https://github.com/Syniurge/Calypso/blob/master/tests/calypso/qt5/moc
For those unfamiliar with Qt, moc (the Meta-Object Compiler) is
a tool that generates additional
On 02/17/2016 06:47 PM, Elie Morisse wrote:
> I now have a working D replacement for moc:
>
> https://github.com/Syniurge/Calypso/blob/master/tests/calypso/qt5/moc
>
> For those unfamiliar with Qt, moc (the Meta-Object Compiler) is a tool
> that generates additional code for Qt classes, code
Hi all,
I now have a working D replacement for moc:
https://github.com/Syniurge/Calypso/blob/master/tests/calypso/qt5/moc
For those unfamiliar with Qt, moc (the Meta-Object Compiler) is a
tool that generates additional code for Qt classes, code then
used by the signal/slot system,
16 matches
Mail list logo
