Re: Interfacing D with C: Getting Started

2017-12-06 Thread Mike Parker via Digitalmars-d-announce
On Wednesday, 6 December 2017 at 08:20:25 UTC, Johan Engelen wrote: Overall I find that it'd be much nicer if you focus on C-D interaction only. Currently you've added a lot of things that people really would already know before reading the text: I think preknowledge should be how to create

Re: Interfacing D with C: Getting Started

2017-12-06 Thread Johan Engelen via Digitalmars-d-announce
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. Hi Mike, Nice. It's always much easier to comment than to write an article from scratch. So take all this with a grain of salt: Overall I find that it'd be

Re: Interfacing D with C: Getting Started

2017-12-05 Thread Arun Chandrasekaran via Digitalmars-d-announce
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?

Re: Interfacing D with C: Getting Started

2017-12-05 Thread Mike Parker via Digitalmars-d-announce
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

Re: Interfacing D with C: Getting Started

2017-12-05 Thread Mike Parker via Digitalmars-d-announce
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

Re: Interfacing D with C: Getting Started

2017-12-05 Thread Mike Parker via Digitalmars-d-announce
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.

Re: Interfacing D with C: Getting Started

2017-12-05 Thread Arun Chandrasekaran via Digitalmars-d-announce
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

Re: Interfacing D with C: Getting Started

2017-12-05 Thread Joakim via Digitalmars-d-announce
the potential problem with long/ulong and C. The blog: https://dlang.org/blog/2017/12/05/interfacing-d-with-c-getting-started/ Reddit: https://www.reddit.com/r/programming/comments/7hqk8b/interfacing_d_with_c_getting_started/ Typo: substitue I think you should change the "long" e

Re: Interfacing D with C: Getting Started

2017-12-05 Thread aberba via Digitalmars-d-announce
the potential problem with long/ulong and C. The blog: https://dlang.org/blog/2017/12/05/interfacing-d-with-c-getting-started/ Reddit: https://www.reddit.com/r/programming/comments/7hqk8b/interfacing_d_with_c_getting_started Thanks. Its something I needs to learn.

Interfacing D with C: Getting Started

2017-12-05 Thread Mike Parker via Digitalmars-d-announce
://dlang.org/blog/2017/12/05/interfacing-d-with-c-getting-started/ Reddit: https://www.reddit.com/r/programming/comments/7hqk8b/interfacing_d_with_c_getting_started/