[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [patch #7683] u32_t should be time_t in some cases
From: |
Mike Pontillo |
Subject: |
[lwip-devel] [patch #7683] u32_t should be time_t in some cases |
Date: |
Fri, 09 Dec 2011 09:06:50 +0000 |
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.121 Safari/535.2 |
Follow-up Comment #2, patch #7683 (project lwip):
That's not a bad approach; thanks. I didn't think of that. But I wondered if
LWIP actually makes assumptions about times being 32-bits, or if all times
should be changed to a possibly system-dependent representation, similar to
what is done with mem_ptr_t.
Anyway, if u32_t is the supported way to go, that's fine. I used the UNIX port
in lwip-contrib as a starting point, so the change could be made there.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/patch/?7683>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/
- [lwip-devel] [patch #7683] u32_t should be time_t in some cases, Mike Pontillo, 2011/12/08
- [lwip-devel] [patch #7683] u32_t should be time_t in some cases, Simon Goldschmidt, 2011/12/09
- [lwip-devel] [patch #7683] u32_t should be time_t in some cases,
Mike Pontillo <=
- [lwip-devel] [patch #7683] u32_t should be time_t in some cases, Simon Goldschmidt, 2011/12/09
- [lwip-devel] [patch #7683] u32_t should be time_t in some cases, Mike Pontillo, 2011/12/12
- [lwip-devel] [patch #7683] u32_t should be time_t in some cases, Simon Goldschmidt, 2011/12/12
- [lwip-devel] [patch #7683] u32_t should be time_t in some cases, Mike Pontillo, 2011/12/12
- [lwip-devel] [patch #7683] u32_t should be time_t in some cases, Mike Pontillo, 2011/12/12
- [lwip-devel] [patch #7683] unix port is missing some explicit casts, Simon Goldschmidt, 2011/12/13