2014-05-03 18:27:38 -04:00
|
|
|
/*
|
2017-06-30 03:22:17 -04:00
|
|
|
* This file is part of the MicroPython project, http://micropython.org/
|
2014-05-03 18:27:38 -04: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 17:14:58 -04:00
|
|
|
#ifndef MICROPY_INCLUDED_LIB_UTILS_PYEXEC_H
|
|
|
|
#define MICROPY_INCLUDED_LIB_UTILS_PYEXEC_H
|
2014-05-03 18:27:38 -04:00
|
|
|
|
2018-01-31 02:21:07 -05:00
|
|
|
#include "py/obj.h"
|
|
|
|
|
2014-03-24 08:23:37 -04:00
|
|
|
typedef enum {
|
|
|
|
PYEXEC_MODE_FRIENDLY_REPL,
|
2020-02-02 09:18:38 -05:00
|
|
|
PYEXEC_MODE_RAW_REPL,
|
2014-03-24 08:23:37 -04:00
|
|
|
} pyexec_mode_kind_t;
|
|
|
|
|
|
|
|
extern pyexec_mode_kind_t pyexec_mode_kind;
|
|
|
|
|
2016-10-16 22:14:59 -04:00
|
|
|
// Set this to the value (eg PYEXEC_FORCED_EXIT) that will be propagated through
|
|
|
|
// the pyexec functions if a SystemExit exception is raised by the running code.
|
|
|
|
// It will reset to 0 at the start of each execution (eg each REPL entry).
|
|
|
|
extern int pyexec_system_exit;
|
|
|
|
|
2014-10-22 02:04:38 -04:00
|
|
|
#define PYEXEC_FORCED_EXIT (0x100)
|
|
|
|
|
2014-03-24 08:23:37 -04:00
|
|
|
int pyexec_raw_repl(void);
|
|
|
|
int pyexec_friendly_repl(void);
|
2014-10-22 14:13:28 -04:00
|
|
|
int pyexec_file(const char *filename);
|
2019-04-26 01:21:09 -04:00
|
|
|
int pyexec_file_if_exists(const char *filename);
|
2023-04-04 15:05:45 -04:00
|
|
|
int pyexec_frozen_module(const char *name, bool allow_keyboard_interrupt);
|
2015-05-05 19:02:58 -04:00
|
|
|
void pyexec_event_repl_init(void);
|
|
|
|
int pyexec_event_repl_process_char(int c);
|
2016-04-01 05:53:50 -04:00
|
|
|
extern uint8_t pyexec_repl_active;
|
2014-03-12 21:06:26 -04:00
|
|
|
|
2019-12-25 02:27:38 -05:00
|
|
|
#if MICROPY_REPL_INFO
|
|
|
|
mp_obj_t pyb_set_repl_info(mp_obj_t o_value);
|
2016-10-17 20:06:20 -04:00
|
|
|
MP_DECLARE_CONST_FUN_OBJ_1(pyb_set_repl_info_obj);
|
2019-12-25 02:27:38 -05:00
|
|
|
#endif
|
2015-11-09 08:13:09 -05: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 17:14:58 -04:00
|
|
|
#endif // MICROPY_INCLUDED_LIB_UTILS_PYEXEC_H
|