public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
* Possible argp implementation questions regarding the use of <stdio.h>
@ 2023-02-02 21:41 Ignacio Vargas
  2023-02-03 12:09 ` Corinna Vinschen
  0 siblings, 1 reply; 2+ messages in thread
From: Ignacio Vargas @ 2023-02-02 21:41 UTC (permalink / raw)
  To: newlib

As I mentioned when I e-mailed from outside the mailing list a while 
ago, I'm working on an very stripped down argp baremetal implementation 
that I would like to contribute to newlib at some point. As Corinna 
pointed out I don't want it to be GPLed so I've been writing an 
implementation from scratch that doesn't even depend on getopt.

I have a question regarding the use (or lack thereof) of <stdio.h>.

Context: For the target we support we can't use newlib's printing 
functions because we can't provide an implementation of all the required 
OS subroutines. This is due to working on a very limited target. This is 
all to say, our stripped down argp can't include <stdio.h>, and in the 
future I would like to contribute it to newlib in a way that doesn't 
require including <stdio.h>.

Question: From what I've been told by colleagues, newlib aims to be a 
very "drop-in" replacement for a regular stdlib. So I'm asking if it 
would be an issue to contribute my argp version that:
1. Already deviates from glibc's in the fact that it's a stripped-down 
version that doesn't implement all the features. And also deviates in 
small ways in certain features it does support.

2. Has an additional mechanism for the user to specify which printing 
function to use, instead of just including <stdio.h> and using the 
provided printing functions. With the goal of having wider support 
across baremetal targets.


Best regards,

Ignacio Vargas


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Possible argp implementation questions regarding the use of <stdio.h>
  2023-02-02 21:41 Possible argp implementation questions regarding the use of <stdio.h> Ignacio Vargas
@ 2023-02-03 12:09 ` Corinna Vinschen
  0 siblings, 0 replies; 2+ messages in thread
From: Corinna Vinschen @ 2023-02-03 12:09 UTC (permalink / raw)
  To: Ignacio Vargas; +Cc: newlib

On Feb  2 15:41, Ignacio Vargas wrote:
> As I mentioned when I e-mailed from outside the mailing list a while ago,
> I'm working on an very stripped down argp baremetal implementation that I
> would like to contribute to newlib at some point. As Corinna pointed out I
> don't want it to be GPLed so I've been writing an implementation from
> scratch that doesn't even depend on getopt.
> 
> I have a question regarding the use (or lack thereof) of <stdio.h>.
> 
> Context: For the target we support we can't use newlib's printing functions
> because we can't provide an implementation of all the required OS
> subroutines. This is due to working on a very limited target. This is all to
> say, our stripped down argp can't include <stdio.h>, and in the future I
> would like to contribute it to newlib in a way that doesn't require
> including <stdio.h>.
> 
> Question: From what I've been told by colleagues, newlib aims to be a very
> "drop-in" replacement for a regular stdlib. So I'm asking if it would be an
> issue to contribute my argp version that:
> 1. Already deviates from glibc's in the fact that it's a stripped-down
> version that doesn't implement all the features. And also deviates in small
> ways in certain features it does support.
> 
> 2. Has an additional mechanism for the user to specify which printing
> function to use, instead of just including <stdio.h> and using the provided
> printing functions. With the goal of having wider support across baremetal
> targets.

Rather than just theorizing about it, what about just sending the
patchset in git format-patch --cover-letter style, so we can discuss
this over the living code?


Corinna


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2023-02-03 12:09 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-02-02 21:41 Possible argp implementation questions regarding the use of <stdio.h> Ignacio Vargas
2023-02-03 12:09 ` Corinna Vinschen

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).