TIL The C Standard does not require malloc() & free() to be reentrant. Just, wow.
-
-
Replying to @kittylyst
@kittylyst Do you really mean reentrant or concurrent?2 replies 0 retweets 0 likes -
Replying to @kittylyst
@kittylyst yes a good implementation should be both reentrant and allow concurrent access.2 replies 0 retweets 0 likes -
Replying to @mjpt777
@mjpt777@kittylyst Don't think it can be re-entrant as it manipulates a shared global resource (memory).2 replies 0 retweets 0 likes -
Replying to @mikeb2701
@mikeb2701@mjpt777@kittylyst Not sure why reentrance a requirement. If used in an ISR you can disable/enable interrupts, mutex otherwise.1 reply 0 retweets 0 likes -
Replying to @darachennis
@darachennis@mikeb2701@kittylyst If one instance is interrupted then other threads can call it without issue, therefore reentrant.1 reply 0 retweets 0 likes
@mjpt777 @mikeb2701 @kittylyst You could use thread-safe as a drop in replacement to reentrant there. Both terms work for me...
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.