The latest post in the D and C series dives into the weeds of D and C strings: how they're implemented, when you need to NUL-terminate your D strings and when you don't, and how the storage of literals in memory allows you to avoid NUL termination in one case you might not have considered and another case that you shouldn't rely on but can in practice with the current compilers.

There are at least two more posts worth of information to go into on this topic, but everything in this post is enough to cover many use cases of D to C string interop.

The blog:
https://dlang.org/blog/2021/05/24/interfacing-d-with-c-strings-part-one/

Reddit:
https://www.reddit.com/r/programming/comments/njyf76/interfacing_d_with_c_strings_part_one/

I always think there is something wrong with the JS of D blog site.
I can't use chrome to open it.

I always think there is something wrong with the JS of D blog site.
I can't use chrome to open it.

On Monday, 24 May 2021 at 14:02:14 UTC, Mike Parker wrote:

Thanks, I wasn't even aware of this.
However, I wish the behavior would be the same between string bounded storage variables and string literals.
I think this would be a good use case for multiple alias this where we would map d types to c types and vice versa.
For strings, it would in case of D->C just add the \0 at the end and for C->D it would be subtracted from the string.

Which posts did you think of?

On Monday, 24 May 2021 at 15:10:46 UTC, sighoya wrote:

I describe them in the Conclusion:

On Monday, 24 May 2021 at 15:03:20 UTC, zjh wrote:

I'm looking at it in Chrome right now. Are you saying it doesn't open at all for you or there are rendering issues, or...?

loading all the time, loading for a long time, but also only part of the load, and still turn the circle.
just like there is a BIG js file .

but ie can open it.
it's strange.