You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
all: Unify header guard usage.
The code conventions suggest using header guards, but do not define how
those should look like and instead point to existing files. However, not
all existing files follow the same scheme, sometimes omitting header guards
altogether, sometimes using non-standard names, making it easy to
accidentally pick a "wrong" example.
This commit ensures that all header files of the MicroPython project (that
were not simply copied from somewhere else) follow the same pattern, that
was already present in the majority of files, especially in the py folder.
The rules are as follows.
Naming convention:
* start with the words MICROPY_INCLUDED
* contain the full path to the file
* replace special characters with _
In addition, there are no empty lines before #ifndef, between #ifndef and
one empty line before #endif. #endif is followed by a comment containing
the name of the guard macro.
py/grammar.h cannot use header guards by design, since it has to be
included multiple times in a single C file. Several other files also do not
need header guards as they are only used internally and guaranteed to be
included only once:
* MICROPY_MPHALPORT_H
* mpconfigboard.h
* mpconfigport.h
* mpthreadport.h
* pin_defs_*.h
* qstrdefs*.h
7 years ago
|
|
|
#ifndef MICROPY_INCLUDED_EXTMOD_LWIP_INCLUDE_ARCH_CC_H
|
|
|
|
|
#define MICROPY_INCLUDED_EXTMOD_LWIP_INCLUDE_ARCH_CC_H
|
|
|
|
|
|
|
|
|
|
#include <stdint.h>
|
|
|
|
|
|
|
|
|
|
// Generate lwip's internal types from stdint
|
|
|
|
|
|
|
|
|
|
typedef uint8_t u8_t;
|
|
|
|
|
typedef int8_t s8_t;
|
|
|
|
|
typedef uint16_t u16_t;
|
|
|
|
|
typedef int16_t s16_t;
|
|
|
|
|
typedef uint32_t u32_t;
|
|
|
|
|
typedef int32_t s32_t;
|
|
|
|
|
|
|
|
|
|
typedef u32_t mem_ptr_t;
|
|
|
|
|
|
|
|
|
|
#define U16_F "hu"
|
|
|
|
|
#define S16_F "hd"
|
|
|
|
|
#define X16_F "hx"
|
|
|
|
|
#define U32_F "u"
|
|
|
|
|
#define S32_F "d"
|
|
|
|
|
#define X32_F "x"
|
|
|
|
|
|
|
|
|
|
#define X8_F "02x"
|
|
|
|
|
#define SZT_F "u"
|
|
|
|
|
|
|
|
|
|
#define BYTE_ORDER LITTLE_ENDIAN
|
|
|
|
|
|
|
|
|
|
#define LWIP_CHKSUM_ALGORITHM 2
|
|
|
|
|
|
|
|
|
|
#include <assert.h>
|
|
|
|
|
#define LWIP_PLATFORM_DIAG(x)
|
|
|
|
|
#define LWIP_PLATFORM_ASSERT(x) { assert(1); }
|
|
|
|
|
|
|
|
|
|
//#define PACK_STRUCT_FIELD(x) x __attribute__((packed))
|
|
|
|
|
#define PACK_STRUCT_FIELD(x) x
|
|
|
|
|
#define PACK_STRUCT_STRUCT __attribute__((packed))
|
|
|
|
|
#define PACK_STRUCT_BEGIN
|
|
|
|
|
#define PACK_STRUCT_END
|
|
|
|
|
|
all: Unify header guard usage.
The code conventions suggest using header guards, but do not define how
those should look like and instead point to existing files. However, not
all existing files follow the same scheme, sometimes omitting header guards
altogether, sometimes using non-standard names, making it easy to
accidentally pick a "wrong" example.
This commit ensures that all header files of the MicroPython project (that
were not simply copied from somewhere else) follow the same pattern, that
was already present in the majority of files, especially in the py folder.
The rules are as follows.
Naming convention:
* start with the words MICROPY_INCLUDED
* contain the full path to the file
* replace special characters with _
In addition, there are no empty lines before #ifndef, between #ifndef and
one empty line before #endif. #endif is followed by a comment containing
the name of the guard macro.
py/grammar.h cannot use header guards by design, since it has to be
included multiple times in a single C file. Several other files also do not
need header guards as they are only used internally and guaranteed to be
included only once:
* MICROPY_MPHALPORT_H
* mpconfigboard.h
* mpconfigport.h
* mpthreadport.h
* pin_defs_*.h
* qstrdefs*.h
7 years ago
|
|
|
#endif // MICROPY_INCLUDED_EXTMOD_LWIP_INCLUDE_ARCH_CC_H
|
