From: "Pedro Falcato" <pedro.falcato@gmail.com>
To: devel@edk2.groups.io, marcin.juszkiewicz@linaro.org
Subject: Re: [edk2-devel] Maybe it is time to update code style?
Date: Mon, 25 Sep 2023 19:03:27 +0100 [thread overview]
Message-ID: <CAKbZUD2m3uFgXu31J2Dhbzsnm1KBbCSuMuq-yduw+AB-PmgSAg@mail.gmail.com> (raw)
In-Reply-To: <f6cc1fc4-0198-4066-9992-294f1ae59e5c@linaro.org>
On Mon, Sep 25, 2023 at 10:03 AM Marcin Juszkiewicz
<marcin.juszkiewicz@linaro.org> wrote:
>
> I feel sick each time I have to edit EDK2 code.
>
> All those INF, DEC, DSC, FDF, XYZ files are something I do not even try
> to understand, just got minimal knowledge what goes where by asking Leif
> (thanks a lot!) and observing build error messages.
I feel you. We've discussed this before (in the ML and on the UEFI
talkbox discord) and there's a large unwillingness to change the build
system, because it's "super extensible" and all that.
I don't like it, but it is what it is.
>
> I got used to UINTN and other weird variable types. No idea where from
> they came from (MS Windows?)
Yes.
>
> But what sucks more is those 2 spaces used for indenting code. Took me
> a while to reming myself when I used such. It was in 90s, when I was
> Amiga programmer and all I had was 720x480px screen.
>
> Last time I looked at calendar it was 2023 year. Maybe it is time to move
> to 4 spaces?
>
> And can someone take a look at config of code obfuscator used for linting?
> It spits out amount of information showing that noone looked at updating it
> to current version:
You're supposed to use the edk2 uncrustify fork that you get *somehow*
(no, I don't remember how, I do remember it was a pain though).
But seriously, speaking as someone with a completely different
personal coding style, the coding style really isn't all that bad (at
the very least, it's tolerable), it's just a bastardized NT-kernel
style, and with uncrustify you can auto-format all your code.
What really pains me is CRLF vs LF, which breaks *every git tool*.
Seriously, applying patches tends to be a pain, at least on Linux.
--
Pedro
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#109048): https://edk2.groups.io/g/devel/message/109048
Mute This Topic: https://groups.io/mt/101570674/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2023-09-25 18:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 9:03 [edk2-devel] Maybe it is time to update code style? Marcin Juszkiewicz
2023-09-25 15:25 ` Michael D Kinney
2023-09-25 15:39 ` Andrew Fish via groups.io
2023-09-25 17:16 ` Rebecca Cran via groups.io
2023-09-25 18:03 ` Pedro Falcato [this message]
2023-09-25 19:22 ` Marcin Juszkiewicz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKbZUD2m3uFgXu31J2Dhbzsnm1KBbCSuMuq-yduw+AB-PmgSAg@mail.gmail.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox