According to reports in the World-Wide Web,
C++26 failed its DIS ballot. Maybe related
to contracts.
To me, it seems obvious that it is up to the caller code to make sure
the preconditions are fulfilled - checking must therefore be on the
caller side, not the callee side.-a If the precondition fails, the bug is
in the caller code.
Le 26/10/2026 |a 15:19, David Brown a |-crit-a:
To me, it seems obvious that it is up to the caller code to make sure
the preconditions are fulfilled - checking must therefore be on the
caller side, not the callee side.-a If the precondition fails, the bug
is in the caller code.
OK, you can point the client as guilty. But that may make your debugging session more difficult, because you don't know if the client will
actually check the preconditions.
The caller needs to know how to properly use an API, right?
Le 26/10/2026 |a 15:19, David Brown a |-crit-a:
To me, it seems obvious that it is up to the caller code to make sure
the preconditions are fulfilled - checking must therefore be on the
caller side, not the callee side.-a If the precondition fails, the bug
is in the caller code.
OK, you can point the client as guilty. But that may make your debugging session more difficult, because you don't know if the client will
actually check the preconditions.
On 11/6/2026 2:47 PM, Oodini wrote:
Le 26/10/2026 |a 15:19, David Brown a |-crit-a:
To me, it seems obvious that it is up to the caller code to make sure
the preconditions are fulfilled - checking must therefore be on the
caller side, not the callee side.-a If the precondition fails, the bug
is in the caller code.
OK, you can point the client as guilty. But that may make your
debugging session more difficult, because you don't know if the client
will actually check the preconditions.
The caller needs to know how to properly use an API, right?
On 07/11/2026 03:49, Chris M. Thomasson wrote:
On 11/6/2026 2:47 PM, Oodini wrote:
Le 26/10/2026 |a 15:19, David Brown a |-crit-a:
To me, it seems obvious that it is up to the caller code to make sure
the preconditions are fulfilled - checking must therefore be on the
caller side, not the callee side.-a If the precondition fails, the bug >>>> is in the caller code.
OK, you can point the client as guilty. But that may make your
debugging session more difficult, because you don't know if the client
will actually check the preconditions.
The caller needs to know how to properly use an API, right?
No the author of the caller does.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 54:17:53 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
3 files (2,684K bytes) |
| Messages: | 285,549 |