Back on duty
Hello "Ookaze" (your name?). Yes, I remember you being quite active in porg / paco issues since long time ago. So in principle I am willing to consider your kind offer to take over the project. But you'd have to meet certain conditions, like keeping it free, simple, and give credit to the original author. Also, since I am no longer familiar with the sourceforge process, you'd have to make the transition to other code hosting platforms yourself. Also, you'd have to establish some contact with the...
Hello everybody. I am David, the creator and maintainer of porg. I wanted you to know that my life has led me far from computer programming lately, so I don't have the time and energy to keep maintaining this project anymore. I am willing to listen to any candidate to take it over. Cheers, ~David. 2022-05-26 16:44 GMT+02:00, Ookaze [email protected]: You're right, iirc this was David's patch back in 2016. I haven't done anything but correct the bug that was very annoying and bit me hard...
Great. Thanks for helping.
I think a simple break after die_help() would do the job. There's no need to call assert(0), because die_help() terminates the program anyway. Done in r189. BTW: I do not react to failed assertions, because they're disabled on stable releases of porg. I just use them on development versions, to help detect errors.
Added break statement on switch, to fix compilation errors
OK. log.c is compiled with gcc, not g++. So we have to add the '-Wno-nonnull-compare' flag to MY_CFLAGS as well. Done in r188.
OK. log.c is compiled with gcc, not g++. So we have to add the '-Wno-nonnull-compare' flag to MY_CFLAGS as well. Done in r188. 2017-08-30 19:46 GMT+02:00, Bat Guano [email protected]: Thank you for keeping this up. Even after make distclean/make clean and autoreconf, compilation ends with the error when log.c is processed. The Makefile in porg-log contains, though: ~~~ cat lib/porg-log/Makefile | grep CXXFLAGS CXXFLAGS = -g -O2 MY_CXXFLAGS = -W -ansi -pedantic -Wall -fno-operator-names -std=c++11...