3 ms·

that is why it was not "static const char buf[]" ;) it was not an accident executable stacks are still common (incl on windows with some settings), and somet

that is why it was not "static const char buf[]" ;) it was not an accident executable stacks are still common (incl on windows with some settings), and sometimes they are required (eg for gcc nested functions)

diamondlovesyou 5mo ago
That won't be located on the stack either. The underlying buffer will be a TU local - ie static and not rx
- lisper 5mo ago
  Good grief, what a useless argument. Isn't it obvious that this could trivially be converted to a non-static array if that's really what was needed?
  - rowanG077 5mo ago
    If you are going to be pedantic, at least be fully pedantic.