Hi, while using getopt() from a task started from NSH I realized subsequent calls reused the global optind and similar variables resulting in different results each time. I'm aware this is expected in FLAT mode and is related to the issue of static C++ constructors (they would only be called once, not every time the task is started).
What I wonder is what could we do to avoid this common pitfall: - document it somewhere (a common issues/troubleshooting section in the docs would be good to have anyways) and just accept the issue - religiously initialize globals myself before being used (a pain, error prone, and a bit adhoc, working only for FLAT mode) - support reentrant versions of all possible APIs and always use these in FLAT mode - devise a mechanism to mimic what would be done by OS in KERNEL mode (add some custom handler to APIs internally using globals, such as getopt, that can be called either manually by user or by the OS itself when the task is started?) - other? Just trying to avoid stepping n-times on the same stone. I think this can also happen to unsuspecting users since a lot of these POSIX interfaces kind of promote these interfaces which use globals internally. Best, Matias
