lwip-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lwip-devel] [patch #9700] move err_t typedef after the defintion of err


From: Jonas Rabenstein
Subject: [lwip-devel] [patch #9700] move err_t typedef after the defintion of err_enum_t
Date: Wed, 10 Oct 2018 18:50:31 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36

URL:
  <https://savannah.nongnu.org/patch/?9700>

                 Summary: move err_t typedef after the defintion of err_enum_t

                 Project: lwIP - A Lightweight TCP/IP stack
            Submitted by: ghostav
            Submitted on: Wed 10 Oct 2018 10:50:30 PM UTC
                Category: None
                Priority: 3 - Low
                  Status: None
                 Privacy: Public
             Assigned to: None
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: None

    _______________________________________________________

Details:

I work on an c++ project and want to use lwIP for it. As I am not memory
constraint and on an 32bit architecture I would like to use the err_enum_t
enum directly as err_t value. Eventually, I could use this to depend on an
actual lwIP error to be given as argument to a function due to the stronger
type checking in C++ where an int is not automatically converted to an enum.



    _______________________________________________________

File Attachments:


-------------------------------------------------------
Date: Wed 10 Oct 2018 10:50:30 PM UTC  Name:
0001-err.h-move-typedef-of-err_t-after-enum-definition.patch  Size: 1KiB   By:
ghostav

<http://savannah.nongnu.org/patch/download.php?file_id=45180>

    _______________________________________________________

Reply to this item at:

  <https://savannah.nongnu.org/patch/?9700>

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]