#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 -----------------------------+---------------------------- Comment (by yourpalal): FWIW, I opened this ticket because this is behaviour that is easy to run into with the suggested use of the layout builders. Once I hit this, it was very difficult to debug because the code looks, inexplicably, as if it is executing out of order when you're in gdb. (Of course, it is executing in the order the compiler wanted, but not the order I wanted/was expecting) Sacrificing the time of our API users on the altar of 'not my problem' seems silly to me. How many C++ programmers know the spec front to back? Even interpreting the spec can be tricky. GCC seems to treat the chained method calls as one single function call, where it prepares all arguments ahead of time, even though it looks to the programmer (or me, at least) like there are many sequential calls happening. Haha, looks like Ingo beat me to the punch, but I will add my voice in anyway! -- Ticket URL: <https://dev.haiku-os.org/ticket/8515#comment:9> Haiku <https://dev.haiku-os.org> Haiku - the operating system.