top | item 45152628 (no title) sgsjchs | 5 months ago A socket. discuss order hn newest spacechild1|5 months ago How so? Doesn't your socket class have a default constructor and a notion of open and closed? sgsjchs|5 months ago If the moves were destructive, I'd design it to have the default constructor call `::socket` and destructor call `::close`. And there wouldn't be any kind of "closed" state. Why would I want it? load replies (1)
spacechild1|5 months ago How so? Doesn't your socket class have a default constructor and a notion of open and closed? sgsjchs|5 months ago If the moves were destructive, I'd design it to have the default constructor call `::socket` and destructor call `::close`. And there wouldn't be any kind of "closed" state. Why would I want it? load replies (1)
sgsjchs|5 months ago If the moves were destructive, I'd design it to have the default constructor call `::socket` and destructor call `::close`. And there wouldn't be any kind of "closed" state. Why would I want it? load replies (1)
spacechild1|5 months ago
sgsjchs|5 months ago