The second release candidate for 0.8.1 is out (the first one was not
announced). 0.8.2 notably contains a HTTP forward proxy, handling
incoming HTTP requests on custom transports and a MongoDB based session
store. On top of that, there are many smaller improvements in the HTTP
server, web/REST
This is the first post in a new tutorial series I'm doing on the
blog. I've covered this topic elsewhere, so for most of the
basics I just link to existing material. The purpose of this
series is to delve into some of the trouble spots that arise from
the differences between the two languages.
very nice to see development going strong
Hi all,
Google Summer of Code (GSoC) 2018 is about to start soon [1] (the
application period for organizations is in January 2018).
Hence, I would very happy about any project ideas you have or
projects which are important to you.
And, of course, if you would be willing to mentor a student,
pl
On Saturday, 2 December 2017 at 08:17:24 UTC, helxi wrote:
On Sunday, 15 October 2017 at 20:18:37 UTC, Mike Wey wrote:
[...]
I highly appreciate that the project is being actively
maintained but I want to express my concern.
It would be really nice if there was an easy tutorial for the
lib
On Tuesday, 5 December 2017 at 16:06:19 UTC, Mike Parker wrote:
This is the first post in a new tutorial series I'm doing on
the blog. I've covered this topic elsewhere, so for most of the
basics I just link to existing material. The purpose of this
series is to delve into some of the trouble s
On Monday, 4 December 2017 at 21:22:39 UTC, Guillaume Piolat
wrote:
On Friday, 1 December 2017 at 18:56:50 UTC, WebFreak001 wrote:
Hi everyone,
I made a public survey (everyone can look at the responses)
and it would be great if you took some time and answered it. I
think it will greatly bene
On Tuesday, 5 December 2017 at 16:06:19 UTC, Mike Parker wrote:
This is the first post in a new tutorial series I'm doing on
the blog. I've covered this topic elsewhere, so for most of the
basics I just link to existing material. The purpose of this
series is to delve into some of the trouble s
In D, long and ulong are always 8 bytes. This lines up with
most 64-bit systems under the version(Posix) umbrella, where
long and unsigned long are also 8 bytes. However, they are 4
bytes on 32-bit architectures. Moreover, they’re always 4 bytes
on Windows, even on a 64-bit architecture.
Why
On Wednesday, 6 December 2017 at 04:14:35 UTC, Arun
Chandrasekaran wrote:
In D, long and ulong are always 8 bytes. This lines up with
most 64-bit systems under the version(Posix) umbrella, where
long and unsigned long are also 8 bytes. However, they are 4
bytes on 32-bit architectures. Moreover
On Wednesday, 6 December 2017 at 01:29:10 UTC, Joakim wrote:
Typo: substitue
And I thought I had managed to catch everything this time. Thanks!
I think you should change the "long" explanation to
"However, in C, they are 4 bytes"
as it may not be clear to some that you're now talking ab
On Wednesday, 6 December 2017 at 04:27:01 UTC, Mike Parker wrote:
On Wednesday, 6 December 2017 at 04:14:35 UTC, Arun
Chandrasekaran wrote:
In D, long and ulong are always 8 bytes. This lines up with
most 64-bit systems under the version(Posix) umbrella, where
long and unsigned long are also 8
On Wednesday, 6 December 2017 at 04:33:38 UTC, Mike Parker wrote:
On Wednesday, 6 December 2017 at 04:27:01 UTC, Mike Parker
wrote:
On Wednesday, 6 December 2017 at 04:14:35 UTC, Arun
Chandrasekaran wrote:
[...]
Why is this? How are we expected to write cross platform code
with long/ulong? W
13 matches
Mail list logo
