On 25/05/2021 3:39 AM, zjh wrote:
> use chrome ,cannot open the DEV.
> press `F12` of no use.
> `Alt+U`of no use.
> continue rotating the small circle.You can do nothing.

There is something seriously wrong with your install then.
It isn't related to the website itself.

On 5/24/21 10:02 AM, Mike Parker wrote:
> 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/ 
> 

Nice article!

Note that there is a huge pitfall awaiting you if you use `toStringz`: garbage collection. You may want to amend the article to identify this pitfall.

And I'm not talking about requiring `@nogc`, I'm talking about the GC collecting the data while C is still using it.

In your example:

```d
puts(s1.toStringz());
```

This leaves a GC-collectible allocation in C land. For `puts`, it's fine, as the data is not used past the call, but in something else that might keep it somewhere not accessible to the GC, you'll want to assign that to a variable that lasts as long as the resource is used.

-Steve

On Monday, 24 May 2021 at 16:16:53 UTC, Steven Schveighoffer wrote:
> On 5/24/21 10:02 AM, Mike Parker wrote:
>> 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/
>> 
>
> Nice article!
>
> Note that there is a huge pitfall awaiting you if you use `toStringz`: garbage collection. You may want to amend the article to identify this pitfall.
>
> And I'm not talking about requiring `@nogc`, I'm talking about the GC collecting the data while C is still using it.
>
> In your example:
>
> ```d
> puts(s1.toStringz());
> ```
>
> This leaves a GC-collectible allocation in C land. For `puts`, it's fine, as the data is not used past the call, but in something else that might keep it somewhere not accessible to the GC, you'll want to assign that to a variable that lasts as long as the resource is used.
>
> -Steve

It’s worse than that, no? If the only reference to GC data isn’t on the stack of a tracked thread, in GC allocated memory or in a tracked root then it can be freed. Even in D:

void foo(int* a) {
    int** b = cast(int**) malloc((int*).sizeof);
    *b = a;
    a = null;
    GC.collect();
    **b = 4; // whoops!!
}

foo(new int);

Right? Obviously that collection could be from calling another function (e.g. a callback from C to D code) or from another thread. Or am I missing something?

On Monday, 24 May 2021 at 16:16:53 UTC, Steven Schveighoffer wrote:

>
> Nice article!

Thanks!

>
> Note that there is a huge pitfall awaiting you if you use `toStringz`: garbage collection. You may want to amend the article to identify this pitfall.
>
> And I'm not talking about requiring `@nogc`, I'm talking about the GC collecting the data while C is still using it.
>
> In your example:
>
> ```d
> puts(s1.toStringz());
> ```
>
> This leaves a GC-collectible allocation in C land. For `puts`, it's fine, as the data is not used past the call, but in something else that might keep it somewhere not accessible to the GC, you'll want to assign that to a variable that lasts as long as the resource is used.
>

That's what I'm referring to in the conclusion where I say this about what's going to be in Part Two:

> how to avoid a potential problem spot that can arise when passing GC-allocated D strings to C

I'll cover approaches to maintaining a reference, like `GC.addRoot`, and emphasize that it applies to any GC-allocated memory, not just strings.

switch to ie.
other websites is no problem.
I don't know why.

On 5/24/21 8:38 PM, Mike Parker wrote:
> On Monday, 24 May 2021 at 16:16:53 UTC, Steven Schveighoffer wrote:

>> This leaves a GC-collectible allocation in C land. For `puts`, it's fine, as the data is not used past the call, but in something else that might keep it somewhere not accessible to the GC, you'll want to assign that to a variable that lasts as long as the resource is used.
>>
> 
> That's what I'm referring to in the conclusion where I say this about what's going to be in Part Two:
> 
>> how to avoid a potential problem spot that can arise when passing GC-allocated D strings to C
> 
> I'll cover approaches to maintaining a reference, like `GC.addRoot`, and emphasize that it applies to any GC-allocated memory, not just strings.

OK, I'm just concerned people will see the pattern:

```d
somecfunc(str.toStringz);
```

and think that's the end of it.

-Steve

On 5/24/21 11:30 PM, surlymoor wrote:
> On Tuesday, 25 May 2021 at 00:58:31 UTC, Steven Schveighoffer wrote:
>> OK, I'm just concerned people will see the pattern:
>>
>> ```d
>> somecfunc(str.toStringz);
>> ```
>>
>> and think that's the end of it.
>>
> 
> Pretty sure its documentation has a conspicuous warning regarding that.

It does, and that's [sometimes ignored](https://forum.dlang.org/post/bogwusbqfewqifjlfmjz@forum.dlang.org), even by [seasoned veterans](https://forum.dlang.org/post/rorsrk$1tdu$1@digitalmars.com).

Anyway, it doesn't hurt to identify the possible memory problems that a function can have when recommending it.

-Steve

On Tuesday, 25 May 2021 at 00:58:31 UTC, Steven Schveighoffer wrote:
> On 5/24/21 8:38 PM, Mike Parker wrote:
> OK, I'm just concerned people will see the pattern:
>
> ```d
> somecfunc(str.toStringz);
> ```
>
> and think that's the end of it.
>

Yeah. Good point. I've updated the post.

On Tuesday, 25 May 2021 at 00:41:50 UTC, zjh wrote:
> switch to ie.
> other websites is no problem.
> I don't know why.

I too faced this problem in my laptop's chrome. I started reading the article in the middle of my work (In my PC's chrome browser). Then after read half of the page, I bookmarked that page and after a few hours, at the mid night, I try to open the bookmarked page in my laptop's chrome browser. But page is partially opened and no text from the article is visible. Only the links in side bar is visible, but they are not clickable. The progress bar is still rotating. So I gave up and did some other tasks.
Then next morning, I have opened the page in my PC's chrome and saved the web page with "Save As" option and send those file to my laptop via dropbox.
Then I tried to open that saved webpage in laptop's chrome. But it did the same thing. No text is visible. It's some time showing a alert that this web page is taking too many time to load, wait or kill ?.
Then I tested that saved web page in Internet Explorer and it opened without any problem.