2014-05-03 22:27:38 +00:00
|
|
|
/*
|
2017-06-30 07:22:17 +00:00
|
|
|
* This file is part of the MicroPython project, http://micropython.org/
|
2014-05-03 22:27:38 +00:00
|
|
|
*
|
|
|
|
* The MIT License (MIT)
|
|
|
|
*
|
|
|
|
* Copyright (c) 2013, 2014 Damien P. George
|
|
|
|
*
|
|
|
|
* Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
|
|
* of this software and associated documentation files (the "Software"), to deal
|
|
|
|
* in the Software without restriction, including without limitation the rights
|
|
|
|
* to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
|
|
* copies of the Software, and to permit persons to whom the Software is
|
|
|
|
* furnished to do so, subject to the following conditions:
|
|
|
|
*
|
|
|
|
* The above copyright notice and this permission notice shall be included in
|
|
|
|
* all copies or substantial portions of the Software.
|
|
|
|
*
|
|
|
|
* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
|
|
* IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
|
|
* FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
|
|
* AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
|
|
* LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
|
|
* OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
|
|
|
|
* THE SOFTWARE.
|
|
|
|
*/
|
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
2017-06-29 21:14:58 +00:00
|
|
|
#ifndef MICROPY_INCLUDED_PY_OBJTUPLE_H
|
|
|
|
#define MICROPY_INCLUDED_PY_OBJTUPLE_H
|
2015-01-01 20:27:54 +00:00
|
|
|
|
|
|
|
#include "py/obj.h"
|
2014-05-03 22:27:38 +00:00
|
|
|
|
2014-01-12 21:23:10 +00:00
|
|
|
typedef struct _mp_obj_tuple_t {
|
|
|
|
mp_obj_base_t base;
|
2017-02-16 05:09:51 +00:00
|
|
|
size_t len;
|
2014-01-12 21:23:10 +00:00
|
|
|
mp_obj_t items[];
|
|
|
|
} mp_obj_tuple_t;
|
|
|
|
|
2015-11-27 13:38:15 +00:00
|
|
|
typedef struct _mp_rom_obj_tuple_t {
|
|
|
|
mp_obj_base_t base;
|
2017-02-16 05:09:51 +00:00
|
|
|
size_t len;
|
2015-11-27 13:38:15 +00:00
|
|
|
mp_rom_obj_t items[];
|
|
|
|
} mp_rom_obj_tuple_t;
|
|
|
|
|
2015-04-09 22:56:15 +00:00
|
|
|
void mp_obj_tuple_print(const mp_print_t *print, mp_obj_t o_in, mp_print_kind_t kind);
|
2017-08-29 03:04:01 +00:00
|
|
|
mp_obj_t mp_obj_tuple_unary_op(mp_unary_op_t op, mp_obj_t self_in);
|
|
|
|
mp_obj_t mp_obj_tuple_binary_op(mp_binary_op_t op, mp_obj_t lhs, mp_obj_t rhs);
|
2014-05-11 17:00:45 +00:00
|
|
|
mp_obj_t mp_obj_tuple_subscr(mp_obj_t base, mp_obj_t index, mp_obj_t value);
|
2016-01-09 23:14:54 +00:00
|
|
|
mp_obj_t mp_obj_tuple_getiter(mp_obj_t o_in, mp_obj_iter_buf_t *iter_buf);
|
2015-01-01 20:27:54 +00:00
|
|
|
|
2015-04-21 14:14:24 +00:00
|
|
|
extern const mp_obj_type_t mp_type_attrtuple;
|
|
|
|
|
|
|
|
#define MP_DEFINE_ATTRTUPLE(tuple_obj_name, fields, nitems, ...) \
|
2015-11-27 13:38:15 +00:00
|
|
|
const mp_rom_obj_tuple_t tuple_obj_name = { \
|
2015-04-21 14:14:24 +00:00
|
|
|
.base = {&mp_type_attrtuple}, \
|
|
|
|
.len = nitems, \
|
2020-02-27 04:36:53 +00:00
|
|
|
.items = { __VA_ARGS__, MP_ROM_PTR((void *)fields) } \
|
2015-04-21 14:14:24 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
#if MICROPY_PY_COLLECTIONS
|
|
|
|
void mp_obj_attrtuple_print_helper(const mp_print_t *print, const qstr *fields, mp_obj_tuple_t *o);
|
|
|
|
#endif
|
|
|
|
|
2017-02-16 05:09:51 +00:00
|
|
|
mp_obj_t mp_obj_new_attrtuple(const qstr *fields, size_t n, const mp_obj_t *items);
|
2015-04-21 14:14:24 +00:00
|
|
|
|
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
2017-06-29 21:14:58 +00:00
|
|
|
#endif // MICROPY_INCLUDED_PY_OBJTUPLE_H
|