Hello Azzeddine
>> "What are the supported functions"
This is a work in progress - As stated in the topic title, we used the word (Towards)
This work is planned for Ring 1.21 release (Under Development)
Currently what works is the Ring Compiler/VM itself
Also, we tried supporting simple functions from GPIO (Just for testing) - And we are happy with the results, So we can continue development.
Later more functions/libraries could be added using Ring Code Generator for Extensions - In a similar way used for supporting other extensions (This will not be hard - We plan to provide good support for the libraries/functions provided by Raspberry Pi Pico C/C++ SDK)
Also, based on your knowledge about Ring extensions, You can support any extra libraries in the future.
The next step will be adding what we did to GitHub and continue adding libraries support.
>> "Great addition this means we can use Arduino"
Currently, we focus on Raspberry Pi Pico
Other/Similar projects could be supported by the community in the future.
>> "I mean are all MicroPython functions supported"
We don't plan to compete with MicroPython - I have full respect for this project, in reality this project is a motivation to any dynamic language community towards using their language on Microcontrollers.
Also, In theory, Ring extensions could grow to the same level or better.
Ring advantages will be
1- Using the same implementation code for Microcontroller, Desktop, Web, WebAssembly, Mobile, etc.
2- Ring Garbage Collector and the language features is already good for embedded systems
3- Ring could be faster & provide better performance (During next releases like Ring 1.21, Ring 1.22, etc.) - But this is not very important compared to the importance of memory usage.
Greetings,
Mahmoud