I am not a attorney, but I seem to recall that a legal reference
reference to a copyright or a trademark require the © and small tm
superscript .
This -- plus the names that Brennan mentions -- are some of the reasons
why unicode really needs to be permitted within comments. None of these
should appear in code.
On 10/10/2022 9:39 AM, Brennan Ashton wrote:
Some of these are are people's names or in documentation, I don't see any
reason to update that. Things like mu or I2C seems reasonable to convert
for searchability.
--Brennan
On Mon, Oct 10, 2022, 8:33 AM Fotis Panagiotopoulos <f.j.pa...@gmail.com>
wrote:
Shall I enhance nxstyle to check for this? Is this the correct place for
this check?
On Mon, Oct 10, 2022 at 6:30 PM Alin Jerpelea <jerpe...@gmail.com> wrote:
Let's remove them!
Thanks for looking into this issue
Best Regards
Alin
On Mon, 10 Oct 2022, 17:25 Alan C. Assis, <acas...@gmail.com> wrote:
Agree! It is better to avoid it.
On 10/10/22, Fotis Panagiotopoulos <f.j.pa...@gmail.com> wrote:
Hello!
A few weeks ago I had some problems with a static analysis tool that
couldn't parse NuttX code, due to non-Unicode characters. I provided
a
couple of PRs and fixed the issues, but it got me thinking...
Do we really need Unicode characters within the codebase?
I can only think of problems with this, from missing glyphs from
fonts,
to
difficulties in search...
I don't see any value in writing μs instead of us, or I²C instead of
I2C.
What do you think?
Shall we allow such characters, or enforce ASCII-only characters in
the
codebase?
