There may be other parts of the code that create threads, depending on how you use them - e.g. SNMP supports netconn mode which creates a thread.
But you don't need to avoid sys_thread_new - just implement this function so it uses your own class to create a thread. Dirk On Sun, Oct 9, 2016 at 7:08 AM, Kenny Koller <kenny.kol...@gmail.com> wrote: > I use C++ and prefer to use a task class that I designed. I do not want to > allocate these statically. It's not clear to me why the network stack would > be concerned with creating threads. I understand that there is a network > thread that is created but I don't want it created by sys_thread_new. > > As far as I can tell there is only one Network task that is created. How > might I rearrange things so that I create that task in my application and > add it's logic? > > Does anyone foresee any issues if I don't support this call? > > Best regards, > > Kenny > > _______________________________________________ > lwip-users mailing list > lwip-users@nongnu.org > https://lists.nongnu.org/mailman/listinfo/lwip-users >
_______________________________________________ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users
