Conversation

Notices

1. Embed this notice
   anna (navi@social.vlhl.dev)'s status on Friday, 21-Feb-2025 09:34:16 JST anna
   i literally can't use posix_spawn with literal strings without warnings
   
   pass a const char *[] it complains about dropping nested pointer qualifiers
   try to build a char *[] = { "foo", NULL }, it complains that "foo" drops qualifiers
   try to cast it, char *[] = { (char *) "foo", NULL }, it *still* complains about dropping qualifiers
   
   i literally can't use this api in a correct way
   • Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Friday, 21-Feb-2025 09:37:45 JST Haelwenn /элвэн/ :triskell:

     in reply to

     @navi Well I'd say -Wwrite-strings doesn't have to always be strictly followed, specially given how many Unix APIs with just a plain char * which you'd typically just pass a string literal.

   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Friday, 21-Feb-2025 09:41:36 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • Haelwenn /элвэн/ :triskell:

     @navi And AFAIK posix_spawn had to use similar signatures as the exec family of functions which are using char *const argv[].

   • Embed this notice
     翠星石 (suiseiseki@freesoftwareextremist.com)'s status on Friday, 21-Feb-2025 19:49:46 JST 翠星石

     in reply to
     @navi (void *)