Re: Calypso and the future of D

2016-12-15 Thread Swoorup Joshi via Digitalmars-d
On Tuesday, 27 January 2015 at 19:34:03 UTC, Laeeth Isharc wrote: On Tuesday, 27 January 2015 at 16:39:40 UTC, Elie Morisse wrote: On Monday, 26 January 2015 at 19:35:11 UTC, Laeeth Isharc wrote: I posted some thoughts on web docs writeup of C+= interface here.

Re: Calypso and the future of D

2015-01-27 Thread Laeeth Isharc via Digitalmars-d
On Tuesday, 27 January 2015 at 16:39:40 UTC, Elie Morisse wrote: On Monday, 26 January 2015 at 19:35:11 UTC, Laeeth Isharc wrote: I posted some thoughts on web docs writeup of C+= interface here.

Re: Calypso and the future of D

2015-01-27 Thread Elie Morisse via Digitalmars-d
On Monday, 26 January 2015 at 19:35:11 UTC, Laeeth Isharc wrote: I posted some thoughts on web docs writeup of C+= interface here. http://forum.dlang.org/thread/fmjehcyzhnirybmnj...@forum.dlang.org#post-fmjehcyzhnirybmnjloj:40forum.dlang.org Do you think we could make binaries of calypso

Re: Calypso and the future of D

2015-01-26 Thread bachmeier via Digitalmars-d
On Monday, 26 January 2015 at 09:58:25 UTC, Ulrich Küttler wrote: On Monday, 26 January 2015 at 08:59:34 UTC, Walter Bright wrote: On 1/26/2015 12:18 AM, Jacob Carlborg wrote: Calypso is not a separate tool. It's a fork of LDC which allows you to directly import/include a C++ header files

Re: Calypso and the future of D

2015-01-26 Thread Elie Morisse via Digitalmars-d
On Monday, 26 January 2015 at 00:37:02 UTC, Walter Bright wrote: Excuse the creator's bias :) I agree that Jacob's description makes things more clear, added!

Re: Calypso and the future of D

2015-01-26 Thread Tofu Ninja via Digitalmars-d
On Monday, 26 January 2015 at 10:16:04 UTC, Walter Bright wrote: On 1/26/2015 1:58 AM, Ulrich =?UTF-8?B?S8O8dHRsZXIi?= kuett...@gmail.com wrote: The idea is just brilliant. I for one am excited about the prospect. Lets please discuss how to get the plugin into D, sooner rather than later. No

Re: Calypso and the future of D

2015-01-26 Thread Laeeth Isharc via Digitalmars-d
On Monday, 26 January 2015 at 16:40:38 UTC, Elie Morisse wrote: On Monday, 26 January 2015 at 00:37:02 UTC, Walter Bright wrote: Excuse the creator's bias :) I agree that Jacob's description makes things more clear, added! I posted some thoughts on web docs writeup of C+= interface here.

Re: Calypso and the future of D

2015-01-26 Thread via Digitalmars-d
On Monday, 26 January 2015 at 08:59:34 UTC, Walter Bright wrote: On 1/26/2015 12:18 AM, Jacob Carlborg wrote: Calypso is not a separate tool. It's a fork of LDC which allows you to directly import/include a C++ header files and use the declarations from within D. No bindings or intermediate

Re: Calypso and the future of D

2015-01-26 Thread Walter Bright via Digitalmars-d
On 1/26/2015 1:58 AM, Ulrich =?UTF-8?B?S8O8dHRsZXIi?= kuett...@gmail.com wrote: The idea is just brilliant. I for one am excited about the prospect. Lets please discuss how to get the plugin into D, sooner rather than later. No language is an island. (Apologies to Nick Hornby and everyone else

Re: Calypso and the future of D

2015-01-26 Thread Walter Bright via Digitalmars-d
On 1/26/2015 12:18 AM, Jacob Carlborg wrote: It works something like this: Given the C++ header file foo.h: void bar(unsigned *); and the C++ source file foo.cpp: void bar(unsigned *p) { } I want to call bar() from my D code in test.d: void main() { uint x;

Re: Calypso and the future of D

2015-01-26 Thread Jacob Carlborg via Digitalmars-d
On 2015-01-26 01:37, Walter Bright wrote: I'm obviously terrible at communicating. Let me try again. Assume that I wrote Calypso, and I was explaining it to you: - Given the C++ header file foo.h: void bar(unsigned *); and the C++ source file

Re: Calypso and the future of D

2015-01-25 Thread Kelly via Digitalmars-d
On Sunday, 25 January 2015 at 10:18:34 UTC, Walter Bright wrote: I'm sorry, but it still far from clear just what Calypso does. Suppose I have a C++ file, test.cpp, that contains: int foo(unsigned *p); How do I use Calypso to interface with that from D: ... what happens here ? ...

Re: Calypso and the future of D

2015-01-25 Thread Walter Bright via Digitalmars-d
On 1/24/2015 5:26 PM, Elie Morisse wrote: The README should be clearer now about what Calypso is supposed to do, links to the showcase example which I improved and expanded with a template partial and explicit spec example, and explains how to build it and link it to a C++ library. (thanks to

Re: Calypso and the future of D

2015-01-25 Thread Walter Bright via Digitalmars-d
On 1/25/2015 1:36 PM, John Colvin wrote: On Sunday, 25 January 2015 at 20:45:26 UTC, Walter Bright wrote: Calypso registers itself as a language plugin, and when parse.c encounters parse.c is not part of my project. Where is parse.c? here?

Re: Calypso and the future of D

2015-01-25 Thread Elie Morisse via Digitalmars-d
On Sunday, 25 January 2015 at 22:45:31 UTC, Walter Bright wrote: Not what I meant. What does parse.c have to do with the user of Calypso? How does the user use Calypso? Where is Calypso? How do I run Calypso? A user of Calypso will be baffled when encountering user documentation of Calypso

Re: Calypso and the future of D

2015-01-25 Thread Elie Morisse via Digitalmars-d
On Sunday, 25 January 2015 at 10:18:34 UTC, Walter Bright wrote: Next, in the README example, it says: $ clang++ -std=c++11 -c showcase.cpp -o showcase.cpp.o $ ar rcs libshowcase.a showcase.cpp.o $ ldc2 -cpp-args -std=c++11 -Llibshowcase.a -L-lstdc++ showcase.d Where's Calypso in that?

Re: Calypso and the future of D

2015-01-25 Thread John Colvin via Digitalmars-d
On Sunday, 25 January 2015 at 20:45:26 UTC, Walter Bright wrote: Calypso registers itself as a language plugin, and when parse.c encounters parse.c is not part of my project. Where is parse.c? here? https://github.com/D-Programming-Language/dmd/blob/master/src/parse.c

Re: Calypso and the future of D

2015-01-25 Thread Walter Bright via Digitalmars-d
On 1/25/2015 3:07 PM, Elie Morisse wrote: On Sunday, 25 January 2015 at 22:45:31 UTC, Walter Bright wrote: Not what I meant. What does parse.c have to do with the user of Calypso? How does the user use Calypso? Where is Calypso? How do I run Calypso? A user of Calypso will be baffled when

Re: Calypso and the future of D

2015-01-25 Thread Andrei Alexandrescu via Digitalmars-d
On 1/25/15 4:37 PM, Walter Bright wrote: On 1/25/2015 3:07 PM, Elie Morisse wrote: On Sunday, 25 January 2015 at 22:45:31 UTC, Walter Bright wrote: Not what I meant. What does parse.c have to do with the user of Calypso? How does the user use Calypso? Where is Calypso? How do I run Calypso?

Re: Calypso and the future of D

2015-01-25 Thread Walter Bright via Digitalmars-d
On 1/25/2015 7:16 AM, Elie Morisse wrote: On Sunday, 25 January 2015 at 10:18:34 UTC, Walter Bright wrote: Next, in the README example, it says: $ clang++ -std=c++11 -c showcase.cpp -o showcase.cpp.o $ ar rcs libshowcase.a showcase.cpp.o $ ldc2 -cpp-args -std=c++11 -Llibshowcase.a

Re: Calypso and the future of D

2015-01-25 Thread Kagamin via Digitalmars-d
On Friday, 23 January 2015 at 18:43:30 UTC, Andrei Alexandrescu wrote: 2. We (or Calypso) define D class counterparts for polymorphic types thrown from C++, notably std::exception and subtypes. N.B. those are D classes, not D structs Wouldn't it be easier with structs? They lack only one

Re: Calypso and the future of D

2015-01-24 Thread Elie Morisse via Digitalmars-d
The README should be clearer now about what Calypso is supposed to do, links to the showcase example which I improved and expanded with a template partial and explicit spec example, and explains how to build it and link it to a C++ library. (thanks to the simple partial spec example a nasty

Re: Calypso and the future of D

2015-01-23 Thread Jacob Carlborg via Digitalmars-d
On 2015-01-23 17:02, Andrei Alexandrescu wrote: We should make the life of plugin writers easy. They do get to decide what other prerequisites their tools have. Are you suggesting to have a general plugin architecture in DMD? That would be very cool, especially if they can be installed as

Re: Calypso and the future of D

2015-01-23 Thread Andrei Alexandrescu via Digitalmars-d
On 1/23/15 8:57 AM, Jacob Carlborg wrote: On 2015-01-23 17:02, Andrei Alexandrescu wrote: We should make the life of plugin writers easy. They do get to decide what other prerequisites their tools have. Are you suggesting to have a general plugin architecture in DMD? It's something worth

Re: Calypso and the future of D

2015-01-23 Thread Elie Morisse via Digitalmars-d
On Friday, 23 January 2015 at 00:24:45 UTC, Andrei Alexandrescu wrote: I think it's important that we enable Calypso (https://github.com/Syniurge/Calypso) and related tooling that interfaces D with other languages, notably C++. A key topic in 2015 for D is playing well with C++. A good C++

Re: Calypso and the future of D

2015-01-23 Thread Andrei Alexandrescu via Digitalmars-d
On 1/23/15 10:27 AM, Elie Morisse wrote: Exception catching is next after the first light of my Ogre3D demo, Clang will probably simplify handling of C++ exceptions a lot. On that front, a coworker gave me a simple idea for integration. 1. All C++ non-polymorphic types thrown cannot be caught

Re: Calypso and the future of D

2015-01-23 Thread Jacob Carlborg via Digitalmars-d
On 2015-01-23 19:43, Andrei Alexandrescu wrote: On that front, a coworker gave me a simple idea for integration. 1. All C++ non-polymorphic types thrown cannot be caught in D 2. We (or Calypso) define D class counterparts for polymorphic types thrown from C++, notably std::exception and

Re: Calypso and the future of D

2015-01-23 Thread Abdulhaq via Digitalmars-d
On Friday, 23 January 2015 at 11:26:07 UTC, Walter Bright wrote: On 1/23/2015 3:22 AM, Abdulhaq wrote: On Friday, 23 January 2015 at 10:53:47 UTC, Walter Bright wrote: Yes, it's tied to clang++. It may not even work on all the platforms we support. But that's no matter for now. When you say

Re: Calypso and the future of D

2015-01-23 Thread Jacob Carlborg via Digitalmars-d
On 2015-01-23 11:52, Walter Bright wrote: Yes, it's tied to clang++. It may not even work on all the platforms we support. But that's no matter for now. At least Clang supports all platforms we support. -- /Jacob Carlborg

Re: Calypso and the future of D

2015-01-23 Thread Walter Bright via Digitalmars-d
On 1/23/2015 2:42 AM, Abdulhaq wrote: Calypso sounds fantastic but seems very tied to one compiler - we all need to know if yourself and Walter are content with that, for instance. Yes, it's tied to clang++. It may not even work on all the platforms we support. But that's no matter for now.

Re: Calypso and the future of D

2015-01-23 Thread Abdulhaq via Digitalmars-d
On Friday, 23 January 2015 at 00:24:45 UTC, Andrei Alexandrescu wrote: I think it's important that we enable Calypso (https://github.com/Syniurge/Calypso) and related tooling that interfaces D with other languages, notably C++. A key topic in 2015 for D is playing well with C++. A good C++

Re: Calypso and the future of D

2015-01-23 Thread Abdulhaq via Digitalmars-d
On Friday, 23 January 2015 at 10:53:47 UTC, Walter Bright wrote: On 1/23/2015 2:42 AM, Abdulhaq wrote: Calypso sounds fantastic but seems very tied to one compiler - we all need to know if yourself and Walter are content with that, for instance. Yes, it's tied to clang++. It may not even

Re: Calypso and the future of D

2015-01-23 Thread Walter Bright via Digitalmars-d
On 1/23/2015 12:34 AM, Max Klyga wrote: I remember Walter arguing against this type of solutions because it requires a C++ compiler to be bundled with D. Yes. Does that mean that now we are adopting this path instead of 'extern(C++)' ? No. I presume it will work much like htod.exe, and

Re: Calypso and the future of D

2015-01-23 Thread Dicebot via Digitalmars-d
On Friday, 23 January 2015 at 10:52:26 UTC, Walter Bright wrote: On 1/23/2015 12:34 AM, Max Klyga wrote: I remember Walter arguing against this type of solutions because it requires a C++ compiler to be bundled with D. Yes. Does that mean that now we are adopting this path instead of

Re: Calypso and the future of D

2015-01-23 Thread Walter Bright via Digitalmars-d
On 1/23/2015 3:22 AM, Abdulhaq wrote: On Friday, 23 January 2015 at 10:53:47 UTC, Walter Bright wrote: Yes, it's tied to clang++. It may not even work on all the platforms we support. But that's no matter for now. When you say for now, does that imply that at some time in the future it may

Re: Calypso and the future of D

2015-01-23 Thread Max Klyga via Digitalmars-d
On 2015-01-23 00:24:44 +, Andrei Alexandrescu said: I think it's important that we enable Calypso (https://github.com/Syniurge/Calypso) and related tooling that interfaces D with other languages, notably C++. A key topic in 2015 for D is playing well with C++. A good C++ interface will

Re: Calypso and the future of D

2015-01-23 Thread Andrei Alexandrescu via Digitalmars-d
On 1/23/15 12:34 AM, Max Klyga wrote: I remember Walter arguing against this type of solutions because it requires a C++ compiler to be bundled with D. It doesn't require as much as makes it usable if you have it. Calypso requires dmd + clang++ is the natural dependency direction. Does

Re: Calypso and the future of D

2015-01-23 Thread Andrei Alexandrescu via Digitalmars-d
On 1/23/15 2:42 AM, Abdulhaq wrote: Calypso sounds fantastic but seems very tied to one compiler - we all need to know if yourself and Walter are content with that, for instance. We should make the life of plugin writers easy. They do get to decide what other prerequisites their tools have.

Re: Calypso and the future of D

2015-01-22 Thread weaselcat via Digitalmars-d
On Friday, 23 January 2015 at 00:24:45 UTC, Andrei Alexandrescu wrote: I think it's important that we enable Calypso (https://github.com/Syniurge/Calypso) and related tooling that Safe to assume this will be LDC only?

Calypso and the future of D

2015-01-22 Thread Andrei Alexandrescu via Digitalmars-d
I think it's important that we enable Calypso (https://github.com/Syniurge/Calypso) and related tooling that interfaces D with other languages, notably C++. A key topic in 2015 for D is playing well with C++. A good C++ interface will give access to a host of mature C++ libraries, starting of

Re: Calypso and the future of D

2015-01-22 Thread H. S. Teoh via Digitalmars-d
On Thu, Jan 22, 2015 at 04:24:44PM -0800, Andrei Alexandrescu via Digitalmars-d wrote: I think it's important that we enable Calypso (https://github.com/Syniurge/Calypso) and related tooling that interfaces D with other languages, notably C++. [...] But first, I want to get better acquainted

Re: Calypso and the future of D

2015-01-22 Thread H. S. Teoh via Digitalmars-d
On Fri, Jan 23, 2015 at 12:33:18AM +, Dicebot via Digitalmars-d wrote: On Friday, 23 January 2015 at 00:31:54 UTC, H. S. Teoh via Digitalmars-d wrote: [...] What exactly is Calypso and what is it supposed to do? The README is unhelpful in this respect. All I can tell is that it's a fork of

Re: Calypso and the future of D

2015-01-22 Thread Dicebot via Digitalmars-d
On Friday, 23 January 2015 at 00:31:54 UTC, H. S. Teoh via Digitalmars-d wrote: On Thu, Jan 22, 2015 at 04:24:44PM -0800, Andrei Alexandrescu via Digitalmars-d wrote: I think it's important that we enable Calypso (https://github.com/Syniurge/Calypso) and related tooling that interfaces D with

Re: Calypso and the future of D

2015-01-22 Thread Paul O'Neil via Digitalmars-d
First, a general increase in quality test coverage. If C++ interop is a priority, it makes sense to focus on ironing out what's already there. I've filed a few bugs over the last 2 months or so and I don't think I'm trying anything too far out there. Some of these are internal compiler errors

Re: Calypso and the future of D

2015-01-22 Thread Jacob Carlborg via Digitalmars-d
On 2015-01-23 01:24, Andrei Alexandrescu wrote: I think it's important that we enable Calypso (https://github.com/Syniurge/Calypso) and related tooling that interfaces D with other languages, notably C++. I could always use some help with DStep [1]. For those who doesn't know, it's an