try to get by with one feature macro

I fucking hate feature macros. Egregious discharge of our
division-of-labor-obsessed society. People should be able to introduce
names. People should be able to give up names to lower levels of
abstraction when they encounter conflicts.

Feature macros seem to exist[1] to support more than two levels of
abstraction. You try to build, one of your libraries fails to build
because of a conflict between it and one level down. You don't want to
modify this library. Just fucking https://catern.com/change_code.html
already. But no, I have to litter my code with feature macros even
though I just want the abstraction the original library provides.

[1] https://man7.org/linux/man-pages/man7/feature_test_macros.7.html
    https://lwn.net/Articles/590381

1 files changed, 0 insertions, 3 deletions

diff --git a/src/teliva.c b/src/teliva.c
index f3e6ceb..81997fc 100644
--- a/src/teliva.c
+++ b/src/teliva.c
@@ -172,7 +172,6 @@ void render_previous_error(void) {
   attroff(COLOR_PAIR(COLOR_PAIR_ERROR));
 }
 
-extern char* strdup(const char* s);
 int report_in_developer_mode(lua_State* L, int status) {
   if (status && !lua_isnil(L, -1)) {
     Previous_error = strdup(lua_tostring(L, -1));  /* memory leak */
@@ -749,8 +748,6 @@ void developer_mode(lua_State* L) {
   /* never returns */
 }
 
-extern int mkstemp(char* template);
-extern FILE* fdopen(int fd, const char* mode);
 void save_editor_state(int rowoff, int coloff, int cy, int cx) {
   if (strlen(Current_definition) == 0) return;
   char outfilename[] = "teliva_editor_state_XXXXXX";