Fix for "the defined(...) macro is already defined" warning being issued in case of nested #eval statements by GrayFace · Pull Request #67 · logological/gpp

GrayFace · 2024-02-23T21:57:39Z

I don't have a code sample ready, but something like this should trigger the warning before the fix:

#define Num1 #eval 5*5
5*5*5 = #eval Num1*5

fix "the defined(...) macro is already defined" warning being issued in case of nested #eval statements

GrayFace · 2024-02-23T21:59:35Z

Update gpp.c

61c8703

fix "the defined(...) macro is already defined" warning being issued in case of nested #eval statements

Provide feedback