#8515: GCC behaviour in method chaining should be documented (easy) -----------------------------+---------------------------- Reporter: yourpalal | Owner: pdziepak Type: enhancement | Status: reopened Priority: normal | Milestone: R1 Component: Documentation | Version: R1/Development Resolution: | Keywords: doxygen Blocked By: | Blocking: Has a Patch: 0 | Platform: All -----------------------------+---------------------------- Changes (by bonefish): * status: closed => reopened * resolution: invalid => Comment: The C++ standard specifies plenty of cases of more or less obscure behavior and I doubt that even among seasoned developers many know them all. The evaluation order of function arguments might be one of the more popularly known one, but it still is not exactly obvious and I'm sure a good percentage of developers isn't aware of it. Combined with the fact that `this` is treated like a regular function argument, I think the percentage is even higher. While I generally agree that we don't need to document such an C++ standard oddity, I think in this case we should. The layout builder API is intentionally designed to result in potentially long expressions that read like linearly processed statements. So the mistake of assuming linear evaluation is easily made and warrants a word of warning in the documentation IMO. -- Ticket URL: <https://dev.haiku-os.org/ticket/8515#comment:8> Haiku <https://dev.haiku-os.org> Haiku - the operating system.