You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If there is no intention to add support for them, I think it should at least be documented as it is quite essential for parsing data in some applications. What's your stance on the issue? Is there any suggested workaround currently?
I have no stance on these functions :). I haven't developed a system that has required them, and you are the first to ask. No technical or ideological reason.
Looking over these functions, one blocker is that I do not actually support FILE or stdin/out/err in this library, so it would be gated on having a suitable solution for that.
Some of the functions, such as sscanf and vsscanf, look like they would be suitable for implementation, however.
Yes, in this regard it is similar to some of the printf functions. sscanf is what I was after in this case. It's not a big deal for me and I can work around it.
Activity
phillipjohnston commentedon Mar 6, 2022
I have no stance on these functions :). I haven't developed a system that has required them, and you are the first to ask. No technical or ideological reason.
phillipjohnston commentedon Mar 6, 2022
picolibc (newlib-nano) has full support. I only mention as an immediate solution - I assume you are here because you do not wish to use newlib.
phillipjohnston commentedon Mar 6, 2022
Looking over these functions, one blocker is that I do not actually support
FILEorstdin/out/errin this library, so it would be gated on having a suitable solution for that.Some of the functions, such as
sscanfandvsscanf, look like they would be suitable for implementation, however.stefanct commentedon Mar 6, 2022
Yes, in this regard it is similar to some of the
printffunctions.sscanfis what I was after in this case. It's not a big deal for me and I can work around it.