Open elfring opened 6 years ago
Hi Markus, can you elaborate on what you mean by the "expected naming convention of the C++ language standard"? These macros are never used anywhere other than for replacing 'pragma once', so I really don't care how they are called. If there is a good reason to change them, then by all means go ahead and do it.
How do you think about to avoid that this software depends on undefined behaviour?
Again, please explain.
I suggest to take another look at the usage of reserved identifiers.
Hi Shai,
The point is, compilers are free to, for example, #define anything of the form _[A-Z]. and .__.* So one should not use this. I break this rule myself and have yet to get bitten by it.
-Victor
On Mar 10, 2018, at 11:19 AM, Shai Halevi notifications@github.com wrote:
Again, please explain.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
How are the chances to improve standard compliance?
I would like to point out that identifiers like “
_CModulus_H_
” and “_FHE_H_
” do not fit to the expected naming convention of the C++ language standard. Would you like to adjust your selection for unique names?