yamt commented on code in PR #14923:
URL: https://github.com/apache/nuttx/pull/14923#discussion_r1857845192
##########
drivers/syslog/Kconfig:
##########
@@ -407,5 +407,25 @@ config SYSLOG_REGISTER
---help---
This option will support register the syslog channel
dynamically.
+config SYSLOG_STDOUT
Review Comment:
> > what kind of "the integrity of printing" are you talking about?
> > after all, syslog and stdout are two separate streams.
> > i suspect you are expecting too much.
>
> 1. This isn't a problem that I've encountered personally. Many
developers in project have been complaining about it. It's a point that needs
to be improved.
maybe the problem is obvious for many developers as you say.
but it isn't for me.
can you please give me a reference?
> > are you saying that my guess is correct? ie. it's a problem in your
application.
>
> 2. Why?
i suggested to fix your application if it's a problem in your application.
you answered it's unrealistic to fix the application.
so i thought you were implying that the premise (it's a problem in your
application) was true.
> Is there any conflict between call which interface with ensuring complete
line output? These are two different issues.
sorry, i don't understand what you mean here. what are two issues?
> > it affects developers by complicating the configuration matrix.
>
> 3. Do you still remember that you submitted over 1,000 commits to fix
the printing issue? [Type mismatch and printf format fixes
#2312](https://github.com/apache/nuttx/pull/2312)? Every time I go through the
git history, I'll see all this junk. could I say that you've affected me?
maybe. sorry for affecting you.
however, the confusion this PR would introduce is in another level, IMO.
applications usually do not expect `fputs(stdout)` and `puts` works so
differently.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
