All of lore.kernel.org
 help / color / mirror / Atom feed
* cfsetispeed and zero baudrate
@ 2021-08-30 10:38 Pali Rohár
  2021-08-30 11:04 ` Alejandro Colomar (man-pages)
  0 siblings, 1 reply; 4+ messages in thread
From: Pali Rohár @ 2021-08-30 10:38 UTC (permalink / raw)
  To: Alejandro Colomar, linux-man

Hello Alejandro!

Currently in cfsetispeed() documentation is written:

  If the input baud rate is set to zero, the input baud rate will be
  equal to the output baud rate.

There is B0 constant which represents "zero baud rate". And also
information that argument for cfsetispeed() (and also cfsetospeed())
must be Bnnn constant.

But above quote documents special handling, "zero" here is really
integer 0 and not pre-defined constant B0.

I think that phrase "If the input baud rate is set to zero" could be
confusing, as based on requirement to use Bnnn constants somebody could
interpret that "zero" as B0.

What do you think, should be above documentation part extended to
express that "zero" is really integer 0 and not constant B0?

Some references:
* glibc really checks for integer 0:
  https://sourceware.org/git/?p=glibc.git;a=blob;f=sysdeps/unix/sysv/linux/speed.c;h=daac5ecde1f3695b8cb178002e8756895406087b;hb=HEAD#l86
* POSIX describes that it is integer 0:
  https://pubs.opengroup.org/onlinepubs/9699919799/functions/tcsetattr.html

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

end of thread, other threads:[~2021-08-31  0:25 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-08-30 10:38 cfsetispeed and zero baudrate Pali Rohár
2021-08-30 11:04 ` Alejandro Colomar (man-pages)
2021-08-30 11:25   ` [PATCH] termios.3: Clarify zero argument for cfsetispeed() Pali Rohár
2021-08-31  0:25     ` Michael Kerrisk (man-pages)

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.