Re: autowrap v0.0.1 - Automatically wrap existing D code for use in Python and Excel
On Sunday, 13 May 2018 at 16:23:49 UTC, Nikos wrote:
I'm trying to wrap drepl
(https://github.com/dlang-community/drepl)
My dub.sdl files is
import autowrap.python;
mixin(
wrapAll(
LibraryName("drepl"),
Modules("drepl.interpreter"),
)
);
I also flagged `export` the interpreter function
export Interpreter!Engine interpreter(Engine)(return scope
Engine e) if (isEngine!Engine)
{
// workaround Issue 18540
return Interpreter!Engine(() @trusted { return move(e);
}());
}
I build the library with python35, but when I import it from
python idle, I cannot access the `interpreter` function at all.
I have the feeling I miss something essential here, but I don't
know what it is.
Any ideas?
Eg turn this into a function and try wrapping this instead:
auto intp = interpreter(dmdEngine());
Re: LDC 1.10.0 beta
On Sunday, 13 May 2018 at 18:12:51 UTC, kinke wrote: Hi everyone, on behalf of the LDC team, I'm glad to announce the first beta for LDC 1.10. The highlights of this version in a nutshell: * Based on D 2.080.0. * Supports DragonFly BSD. * Some fixes, most notably wrt. exception stack traces on Linux. Full release log and downloads: https://github.com/ldc-developers/ldc/releases/tag/v1.10.0-beta1 Thanks to all contributors! very good, come on! i mainly use LDC to work now.
Re: serialport v1.0.0
On Sunday, 13 May 2018 at 18:05:35 UTC, Jonathan M Davis wrote: On Sunday, May 13, 2018 17:57:56 Andre Pany via Digitalmars-d-announce wrote: On Sunday, 6 May 2018 at 22:02:05 UTC, Oleg B wrote: > Stable version of serialport package > > * Blocking `SerialPortBlk` for classic usage > > * Non-blocking `SerialPortNonBlk` and `SerialPortFR` for > usage in fibers or in vibe-d > > * Variative initialization and configuration > > * Hardware flow control config flag > > Doc: http://serialport.dpldocs.info/v1.0.0/serialport.html > Dub: http://code.dlang.org/packages/serialport > Git: https://github.com/deviator/serialport Thanks for this library. The announcement is at the right time as I want to write a smart home application to control my shutters. The application will run on a raspberry pi (ftdi sub stick). So, now we'll be able to hack your shutters? ;) Do you thought about including your library into phobos? A std library really should contain this functionality. Really? If the consensus is that it should go in, then okay, but I don't think that I've ever seen a standard library with anything like functionality for talking to serial ports. And what would having it be in Phobos buy you over just grabbing it from code.dlang.org? - Jonathan M Davis Hopefully not:) For me it is just a convenience reason. I would not have to search dub registry for serial libraries and try them out. For functionality included in Phobos I know they were reviewed by several developers and therefore have high code quality and only few bugs. Kind regards Andre
Re: LDC 1.10.0 beta
On Sunday, 13 May 2018 at 18:12:51 UTC, kinke wrote: * Based on D 2.080.0. Great!
LDC 1.10.0 beta
Hi everyone, on behalf of the LDC team, I'm glad to announce the first beta for LDC 1.10. The highlights of this version in a nutshell: * Based on D 2.080.0. * Supports DragonFly BSD. * Some fixes, most notably wrt. exception stack traces on Linux. Full release log and downloads: https://github.com/ldc-developers/ldc/releases/tag/v1.10.0-beta1 Thanks to all contributors!
Re: serialport v1.0.0
On Sunday, May 13, 2018 17:57:56 Andre Pany via Digitalmars-d-announce wrote: > On Sunday, 6 May 2018 at 22:02:05 UTC, Oleg B wrote: > > Stable version of serialport package > > > > * Blocking `SerialPortBlk` for classic usage > > > > * Non-blocking `SerialPortNonBlk` and `SerialPortFR` for usage > > in fibers or in vibe-d > > > > * Variative initialization and configuration > > > > * Hardware flow control config flag > > > > Doc: http://serialport.dpldocs.info/v1.0.0/serialport.html > > Dub: http://code.dlang.org/packages/serialport > > Git: https://github.com/deviator/serialport > > Thanks for this library. The announcement is at the right time as > I want to write a smart home application to control my shutters. > The application will run on a raspberry pi (ftdi sub stick). So, now we'll be able to hack your shutters? ;) > Do you thought about including your library into phobos? A std > library really should contain this functionality. Really? If the consensus is that it should go in, then okay, but I don't think that I've ever seen a standard library with anything like functionality for talking to serial ports. And what would having it be in Phobos buy you over just grabbing it from code.dlang.org? - Jonathan M Davis
Re: serialport v1.0.0
On Sunday, 6 May 2018 at 22:02:05 UTC, Oleg B wrote: Stable version of serialport package * Blocking `SerialPortBlk` for classic usage * Non-blocking `SerialPortNonBlk` and `SerialPortFR` for usage in fibers or in vibe-d * Variative initialization and configuration * Hardware flow control config flag Doc: http://serialport.dpldocs.info/v1.0.0/serialport.html Dub: http://code.dlang.org/packages/serialport Git: https://github.com/deviator/serialport Thanks for this library. The announcement is at the right time as I want to write a smart home application to control my shutters. The application will run on a raspberry pi (ftdi sub stick). Do you thought about including your library into phobos? A std library really should contain this functionality. Kind regards Andre
Re: serialport v1.0.0
On Wednesday, 9 May 2018 at 14:41:45 UTC, Andrea Fontana wrote: On Sunday, 6 May 2018 at 22:02:05 UTC, Oleg B wrote: Stable version of serialport package * Blocking `SerialPortBlk` for classic usage * Non-blocking `SerialPortNonBlk` and `SerialPortFR` for usage in fibers or in vibe-d * Variative initialization and configuration * Hardware flow control config flag Doc: http://serialport.dpldocs.info/v1.0.0/serialport.html Dub: http://code.dlang.org/packages/serialport Git: https://github.com/deviator/serialport I wonder if someone can benchmark serialport lib against this test: http://codeandlife.com/2012/07/03/benchmarking-raspberry-pi-gpio-speed/ I think it's different things. serialport is wrap around system calls, it's not control hardware directly. You could be misled by the phrase about 'hardware flow control': is't set on or off using of RTS and CTS pins of UART. Firmware control RTS and CTS pins directly. http://www.brainboxes.com/faq/items/what-is-rts--cts-hardware-flow-control-
Re: autowrap v0.0.1 - Automatically wrap existing D code for use in Python and Excel
I'm trying to wrap drepl
(https://github.com/dlang-community/drepl)
My dub.sdl files is
import autowrap.python;
mixin(
wrapAll(
LibraryName("drepl"),
Modules("drepl.interpreter"),
)
);
I also flagged `export` the interpreter function
export Interpreter!Engine interpreter(Engine)(return scope
Engine e) if (isEngine!Engine)
{
// workaround Issue 18540
return Interpreter!Engine(() @trusted { return move(e); }());
}
I build the library with python35, but when I import it from
python idle, I cannot access the `interpreter` function at all.
I have the feeling I miss something essential here, but I don't
know what it is.
Any ideas?
