[D-Programming-Deimos] Review process?

[Gor Gyolchanyan]

Using SWIG for porting C libraries to D is like using a chainsaw for
vascular incisions: It's extremely heavy and unproductive.
This is all because SWIG generates intermediate binary, which forwards
calls to C functions, which is completely unnecessary.
Furthermore, It translates macro constants into lists of const
variables. This is very unproductive as well, because macro
definitions don't have addresses and const variables do. A human
translator would've put those in a single enum (providing a whole
bunch of extra functionality, like obtaining the string of the enum
symbols).

On Tue, Nov 8, 2011 at 2:47 PM, Andrea Fontana <advmail at katamail.com> wrote:
> Could the same idea (of a single repository) be extended to support swig
> based portings?
> I've tried to port one of my project (quite complex data access layer) to D
> using swig, and it works fine (and it's quite easy to do).
> It would be useful for c++ class-based libraries...
>
> Il giorno mar, 08/11/2011 alle 14.08 +0400, Gor Gyolchanyan ha scritto:
>
> The first one is handy because you can have everything you want in a
> single place and don't need to clone every lib separately.
> The second one is handy because you don't have to carry around tons of
> unneeded code.
>
> For that reason, I propose us to keep the code in separate
> repositories and refer to them from a single repository in the form of
> submodules.
>
> On Tue, Nov 8, 2011 at 2:00 PM, mta`chrono <chrono at mta-international.net
>> wrote:
>> Does anyone know the last state of Deimos? What are we going to use now.
>>
>> This: https://github.com/D-Programming-Language/deimos
>> Or that: https://github.com/D-Programming-Deimos/
>>
>>
>