Neal Becker Wrote:
> BCS wrote:
>
> > Hello Neal,
> >
> >> My main interest is building python-callable modules (which I
> >> currently do with C++/boost::python). Problem is, D can't be used for
> >> this, because it can't produce shared libraries (except on i386).
> >> This is, as I understan
Neal Becker:
> Yes, I'm very interested in pyd. Is this still actively
> developed/maintained/used?
It used to work well enough on D1. I have used it some times, Pyd was one of my
motivations to learn D in the first place, because writing Python extensions in
D with Pyd is for me much better t
BCS wrote:
> Hello Neal,
>
>> My main interest is building python-callable modules (which I
>> currently do with C++/boost::python). Problem is, D can't be used for
>> this, because it can't produce shared libraries (except on i386).
>> This is, as I understand it, because the D library/librarie
On 2010-06-29 00:45, Neal Becker wrote:
Sean Kelly wrote:
Jacob Carlborg Wrote:
On 2010-06-23 15:42, Neal Becker wrote:
My main interest is building python-callable modules (which I currently
do
with C++/boost::python). Problem is, D can't be used for this, because
it
can't produce shared l
Sean Kelly wrote:
> Jacob Carlborg Wrote:
>
>> On 2010-06-23 15:42, Neal Becker wrote:
>> > My main interest is building python-callable modules (which I currently
>> > do
>> > with C++/boost::python). Problem is, D can't be used for this, because
>> > it
>> > can't produce shared libraries (exc
On 2010-06-24 21:20, Sean Kelly wrote:
Jacob Carlborg Wrote:
On 2010-06-23 15:42, Neal Becker wrote:
My main interest is building python-callable modules (which I currently do
with C++/boost::python). Problem is, D can't be used for this, because it
can't produce shared libraries (except on i
Jacob Carlborg Wrote:
> On 2010-06-23 15:42, Neal Becker wrote:
> > My main interest is building python-callable modules (which I currently do
> > with C++/boost::python). Problem is, D can't be used for this, because it
> > can't produce shared libraries (except on i386). This is, as I understa
On 2010-06-23 15:42, Neal Becker wrote:
My main interest is building python-callable modules (which I currently do
with C++/boost::python). Problem is, D can't be used for this, because it
can't produce shared libraries (except on i386). This is, as I understand
it, because the D library/librar
Hello Neal,
My main interest is building python-callable modules (which I
currently do with C++/boost::python). Problem is, D can't be used for
this, because it can't produce shared libraries (except on i386).
This is, as I understand it, because the D library/libraries are not
built as PIC.
Neal Becker wrote:
My main interest is building python-callable modules (which I currently do
with C++/boost::python). Problem is, D can't be used for this, because it
can't produce shared libraries (except on i386). This is, as I understand
it, because the D library/libraries are not built a
== Quote from Neal Becker (ndbeck...@gmail.com)'s article
> My main interest is building python-callable modules (which I currently do
> with C++/boost::python). Problem is, D can't be used for this, because it
> can't produce shared libraries (except on i386). This is, as I understand
> it, beca
My main interest is building python-callable modules (which I currently do
with C++/boost::python). Problem is, D can't be used for this, because it
can't produce shared libraries (except on i386). This is, as I understand
it, because the D library/libraries are not built as PIC.
This issue h
12 matches
Mail list logo
