Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[threadx-dev] Deprecated APIs - compile-time warnings

Hi everyone.

While working on a draft security advisory, we noticed that the reporter had correctly identified an issue, but that it involved a deprecated API which had been completely superseded by others. Consequently, we closed the draft advisory.

To avoid a repetition of this scenario, I scanned our documentation to identify all deprecated APIs. I then submitted PRs to add compile-time warnings flagging their use. 

The relevant PRs are listed below:
https://github.com/eclipse-threadx/threadx/pull/559
https://github.com/eclipse-threadx/threadx/pull/562
https://github.com/eclipse-threadx/filex/pull/95
https://github.com/eclipse-threadx/usbx/pull/269
https://github.com/eclipse-threadx/guix/pull/167

I also updated the documentation so that it would provide proper context and alternatives for each deprecated API. Also, the documentation now clearly states not to use the APIs in question. 
https://github.com/eclipse-threadx/rtos-docs-asciidoc/pull/32
https://github.com/eclipse-threadx/rtos-docs-asciidoc/pull/33

Those PRs will be merged into the dev branch in the upcoming weeks and will ship in the v6.5.2.202603 release in September.

We intend to completely remove those deprecated APIs in our next minor version (6.6.x), which I expect will be published in 2027 at the earliest. At the same time, we will remove all Azure IoT code from NetX Duo as well as the old HTTP server, which is replaced by the web server. 

Let me know if we missed other deprecated APIs, or if you have feedback about this plan.

(Additionally, Happy Canada Day!)

Best Regards,

Frédéric DESBIENS

Project Lead | Eclipse ThreadX  

Senior Manager — Embedded and IoT | Eclipse Foundation

Mastodon: @fdesbiens@xxxxxxxxxxxxxxxxxxxxx

Eclipse Foundation: The Community for Open Innovation and Collaboration


Back to the top