Re: DConf 2017 Early Bird Registration expires Monday!

[via Digitalmars-d-announce]

On Sunday, 26 February 2017 at 18:59:41 UTC, Walter Bright wrote:

On 2/26/2017 10:03 AM, Petar Kirov [ZombineDev] wrote:
On Saturday, 25 February 2017 at 07:02:48 UTC, Walter Bright 
wrote:

http://dconf.org/2017/registration.html

Don't forget, it goes up to $400 after Monday.


Hello, I just tried to purchase a ticket, however I got a 
'sales ended' message.
I suppose that even though it is not Monday yet, I am late. If 
I can't purchase

an early bird ticket, how can I purchase a normal one?


Looks like I botched up the ending date in Eventbrite. Fixed 
it. Sorry about that.


Thank you very much, Walter! I just bought my ticket. See you 
there :)

Re: DConf 2017 Early Bird Registration expires Monday!

[Walter Bright via Digitalmars-d-announce]

On 2/26/2017 10:03 AM, Petar Kirov [ZombineDev] wrote:

On Saturday, 25 February 2017 at 07:02:48 UTC, Walter Bright wrote:

http://dconf.org/2017/registration.html

Don't forget, it goes up to $400 after Monday.


Hello, I just tried to purchase a ticket, however I got a 'sales ended' message.
I suppose that even though it is not Monday yet, I am late. If I can't purchase
an early bird ticket, how can I purchase a normal one?


Looks like I botched up the ending date in Eventbrite. Fixed it. Sorry about 
that.

Re: DConf 2017 Early Bird Registration expires Monday!

[via Digitalmars-d-announce]

On Saturday, 25 February 2017 at 07:02:48 UTC, Walter Bright 
wrote:

http://dconf.org/2017/registration.html

Don't forget, it goes up to $400 after Monday.


Hello, I just tried to purchase a ticket, however I got a 'sales 
ended' message. I suppose that even though it is not Monday yet, 
I am late. If I can't purchase an early bird ticket, how can I 
purchase a normal one?

mysql-native v1.0.0: Big refresh

[Nick Sabalausky (Abscissa) via Digitalmars-d-announce]

mysql-native is now officially at v1.0.0!

https://github.com/mysql-d/mysql-native

mysql-native is a native D client driver for MySQL and MariaDB, usable 
either with or without vibe.d. It does not rely on the official C 
libraries, instead communicating directly with the server via the 
published MySQL client/server protocol.


This release is equal to rc4, but compared to the last official release, 
v0.1.7, this is a big update.


Summary of changes since v0.1.7:
- API overhauled for better safety, reliability and ease-of-use.
- Deprecated and replaced entire Command struct with better design.
- Better handling of null.
- Improved/expanded docs.
- Various bugs fixed.
- More rigorous test suite.

Users of v0.1.7 should find that most, if not all, of their code still 
works, albiet with many deprecation messages directing them to the newer 
equivalents. The old, deprecated APIs will be removed in a future 
release, but are still usable in v1.0.0.


Full changelog is here:
https://github.com/mysql-d/mysql-native/blob/master/CHANGELOG.md

Overview and example code:
https://github.com/mysql-d/mysql-native/blob/master/README.md

API reference:
http://semitwist.com/mysql-native

Usage in dub:
dependency "mysql-native" version="~>1.0.0"

expat-d 0.1.0

[Moritz Maxeiner via Digitalmars-d-announce]

The package[1] is a binding to the Expat XML parser[2] with no 
high level wrappers, just plain C API.
The initial release covers all of expat 2.2.0 and you need to 
link against the appropriate library yourself.
The compile-time versions XML_UNICODE, XML_UNICODE_WCHAR_T, and 
XML_LARGE_SIZE correspond to the C defines by the same name; use 
them to match the binding to how expat has been compiled.


Rationale as to why this package: I needed a fast, (time) tested 
XML stream parser to use for XMPP parsing and so far I found no 
current D package for that.


[1] https://code.dlang.org/packages/expat-d
[2] http://www.libexpat.org/

Re: DCompute - Native heterogeneous computing for D - is here!

[jmh530 via Digitalmars-d-announce]

On Sunday, 26 February 2017 at 08:37:29 UTC, Nicholas Wilson 
wrote:
DCompute is an extension to LDC capable of generating code 
(with no language changes*) for NVIDIA's NVPTX for use with 
CUDA, SPIRV for use with the OpenCL runtime, and of course the 
host, all at the same time! It is also possible to share 
implementation of algorithms across the host and device.
This will enable writing kernels in D utilising all of D's meta 
programming goodness across the device divide and will allow 
launching those kernels with a level of ease on par with CUDA's 
<<<...>>> syntax. I hope to be giving a talk at DConf2017 about 
this ;), what it enables us to do, what still needs to be done 
and future plans.


Great work.

Schema for ndslice internals

[Ilya Yaroshenko via Digitalmars-d-announce]

https://github.com/libmir/mir-algorithm/blob/master/README.md

Re: DCompute - Native heterogeneous computing for D - is here!

[Rory McGuire via Digitalmars-d-announce]

On Sun, Feb 26, 2017 at 10:37 AM, Nicholas Wilson via
Digitalmars-d-announce  wrote:
> DCompute is an extension to LDC capable of generating code (with no language
> changes*) for NVIDIA's NVPTX for use with CUDA, SPIRV for use with the
> OpenCL runtime, and of course the host, all at the same time! It is also
> possible to share implementation of algorithms across the host and device.
> This will enable writing kernels in D utilising all of D's meta programming
> goodness across the device divide and will allow launching those kernels
> with a level of ease on par with CUDA's <<<...>>> syntax. I hope to be
> giving a talk at DConf2017 about this ;), what it enables us to do, what
> still needs to be done and future plans.
>

Awesome! Been wanting this feature since ldc started catching up to dmd.

DCompute - Native heterogeneous computing for D - is here!

[Nicholas Wilson via Digitalmars-d-announce]

DCompute is an extension to LDC capable of generating code (with 
no language changes*) for NVIDIA's NVPTX for use with CUDA, SPIRV 
for use with the OpenCL runtime, and of course the host, all at 
the same time! It is also possible to share implementation of 
algorithms across the host and device.
This will enable writing kernels in D utilising all of D's meta 
programming goodness across the device divide and will allow 
launching those kernels with a level of ease on par with CUDA's 
<<<...>>> syntax. I hope to be giving a talk at DConf2017 about 
this ;), what it enables us to do, what still needs to be done 
and future plans.


DCompute supports all of OpenCL except Images and Pipes (support 
is planned though).
I haven't done any test for CUDA so I'm not sure about the extent 
of support for it, all of the math stuff works, images/textures 
not so sure.


Many thanks to the ldc team (especially Johan) for their guidance 
and patience, Ilya for reminding me that I should upstream my 
work and John Colvin for his DConf2016 talk for making me think 
'surely compiler support can't be too hard'. 10 months later: 
here it is!


The DCompute compiler is available at the dcompute branch of ldc 
[0], you will need my fork of llvm here[1] and the SPIRV 
submodule that comes with it [2] as the llvm to link against. 
There is also a tool for interconversion [3] (I've mucked up the 
submodules a bit, sorry, just clone it into 'tools/llvm-spirv', 
it's not necessary anyway). The device standard library and 
drivers (both WIP) are available here[4].


Please sent bug reports to their respective components, although 
I'm sure I'll see them anyway regardless of where they go.


[0]: https://github.com/ldc-developers/ldc/tree/dcompute
[1]: https://github.com/thewilsonator/llvm/tree/compute
[2]: https://github.com/thewilsonator/llvm-target-spirv
[3]: https://github.com/thewilsonator/llvm-tool-spirv
[4]: https://github.com/libmir/dcompute

* modulo one hack related to resolving intrinsics because there 
is no static context (i.e. static if) for the device(s). 
Basically a 'codegen time if'.