[lwip-devel] [bug #55405] Usage of uint8_t instead of ui8_t in TCP code

[Oldrich Jedlicka]

URL:
  <https://savannah.nongnu.org/bugs/?55405>

                 Summary: Usage of uint8_t instead of ui8_t in TCP code
                 Project: lwIP - A Lightweight TCP/IP stack
            Submitted by: oldium
            Submitted on: Sun 06 Jan 2019 07:35:40 PM UTC
                Category: TCP
                Severity: 3 - Normal
              Item Group: Faulty Behaviour
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: None
            lwIP version: 2.1.1

    _______________________________________________________

Details:

I am using LWIP 2.1.2 and also LWIP_NO_STDINT_H == 1.

There are 3 functions in TCP code (tcp.c) that use uint8_t type instead of
ui8_t:

tcp_ext_arg_set_callbacks
tcp_ext_arg_set
tcp_ext_arg_get

Expected is that all three functions use ui8_t, because uint8_t is otherwise
unused anywhere else in lwip code (and it is not present on my platform,
unfortunately).




    _______________________________________________________

Reply to this item at:

  <https://savannah.nongnu.org/bugs/?55405>

_______________________________________________
  Message sent via Savannah
  https://savannah.nongnu.org/