On 2021-11-16, goldsi...@gmx.de wrote:
> Am 15.11.2021 um 18:03 schrieb Grant Edwards:
>> Is it required that sys_thread_t be a pointer or integer type?
>>
>> The documentation doesn't state that. The example implementation at
>> https://lwip.fandom.com/wiki/Porting_for_an_OS#Threads shows it as a
Am 15.11.2021 um 18:03 schrieb Grant Edwards:
Is it required that sys_thread_t be a pointer or integer type?
The documentation doesn't state that. The example implementation at
https://lwip.fandom.com/wiki/Porting_for_an_OS#Threads shows it as a
struct, and in the freeRTOS port it's a struct.
B
I feel the port assumes thread creation should always be a success and if
fails then assert is called. So the return value is always non zero. I
believe this cannot be used in a production scenario where error needs to
be reported and mitigated properly depending on what kind of system are you
work
On 2021-11-15, Ajay Bhargav via lwip-users wrote:
> You can define it as integer or pointer based on your system.
Yes, I know I can.
I want to know if it is _required_ to be an integer or pointer.
> Its definately not a structure.
It definitely is a structure in the freeRTOS port which I was
You can define it as integer or pointer based on your system. Its
definately not a structure.
Regards,
Ajay Bhargav
On Mon, Nov 15, 2021, 10:36 PM Grant Edwards
wrote:
> Is it required that sys_thread_t be a pointer or integer type?
>
> The documentation doesn't state that. The example implemen
Is it required that sys_thread_t be a pointer or integer type?
The documentation doesn't state that. The example implementation at
https://lwip.fandom.com/wiki/Porting_for_an_OS#Threads shows it as a
struct, and in the freeRTOS port it's a struct.
But the test code assumes it's a pointer or integ
