[haiku-bugs] Re: [Haiku] #16858: Tidy-up of TRACE Macros in Bootloader (and possibly elsewhere)?
- From: "Haiku" <trac@xxxxxxxxxxxx>
- To: undisclosed-recipients: ;
- Date: Sun, 04 Apr 2021 08:52:16 -0000
#16858: Tidy-up of TRACE Macros in Bootloader (and possibly elsewhere)?
---------------------------------+-------------------------------
Reporter: stellarpower | Owner: nobody
Type: task | Status: new
Priority: normal | Milestone: Unscheduled
Component: System/Boot Loader | Version: R1/Development
Resolution: | Keywords: Formatting, TRACE
Blocked By: | Blocking:
Platform: All |
---------------------------------+-------------------------------
Comment (by pulkomandy):
Replying to [comment:3 stellarpower]:
I probably fall in the camp that it should be included in the macro body
and the call should be left bare, again, when it's implicit that the macro
is a statement or self-contained, because they stand out differently to
function calls and my view is that I'd want the user to be as aware as
possible tjhat it's a macro and thus to be mindful it's not a perfect
system that may have some odd behaviour compared to things in the
compiler-realm. Also, whilst less flexible, it keeps more in our realm of
control.
I prefer that we write the macro in a way that it behaves like a function.
The logic is to put the quirks and unusual things inside the macro, which
is written only once, and then we can use it "normally" (exactly like a
function call). It makes a lot more of the code easier to follow.
--
Ticket URL: <
https://dev.haiku-os.org/ticket/16858#comment:9>
Haiku <
https://dev.haiku-os.org>
The Haiku operating system.
Other related posts:
