LEWGI Cologne: Why isn't is_open const?

JeffGarland / liaw2019-process

Repository for initial drafting of boost.process standards paper

MIT License

5 stars 4 forks source link

LEWGI Cologne: Why isn't is_open const? #32

Closed JeffGarland closed 4 years ago

JeffGarland commented 4 years ago

I believe the answer here is that the process can complete during the is_open check and hence the process object needs to be updated.

@klemens-morgenstern can you confirm?

klemens-morgenstern commented 4 years ago

Yes, BUT we wouldn't need that to be the case, since we could have the _exit_code member (that can be changed) be mutable.

JeffGarland commented 4 years ago

Yep, but it's sorta a facade because that makes people think its thread safe. I"m not going to add it to the paper, but just want to to make sure I understood why it's that way currently.