Mirrors/fish-shell
2
0
Fork 0
mirror of https://github.com/fish-shell/fish-shell synced 2024-12-29 14:23:09 +00:00
Code Issues Projects Releases Packages Wiki Activity
fish-shell/src/tinyexpr.h

104 lines
2.6 KiB
C
Raw Normal View History

Replace muparser with tinyexpr
2018-02-10 18:46:34 +00:00
/*
* TINYEXPR - Tiny recursive descent parser and evaluation engine in C
*
* Copyright (c) 2015, 2016 Lewis Van Winkle
*
* http://CodePlea.com
*
* This software is provided 'as-is', without any express or implied
* warranty. In no event will the authors be held liable for any damages
* arising from the use of this software.
*
* Permission is granted to anyone to use this software for any purpose,
* including commercial applications, and to alter it and redistribute it
* freely, subject to the following restrictions:
*
* 1. The origin of this software must not be misrepresented; you must not
* claim that you wrote the original software. If you use this software
* in a product, an acknowledgement in the product documentation would be
* appreciated but is not required.
* 2. Altered source versions must be plainly marked as such, and must not be
* misrepresented as being the original software.
* 3. This notice may not be removed or altered from any source distribution.
*/
[tinyexpr] Add error handling This turns a bunch of ifs on their heads. We often see this pattern in te: ```c if (s->type != SOME_TYPE) { // error handling } else { // normal code } ``` Only, since we want to return the first error, we do ```c if (s->type == SOME_TYPE) { // normal code } else if (s->type != TOK_ERROR) { // Add a new error - if it already has type error // this should already be handled. } ``` One big issue is the comma operator, that means arity-1 functions can take an arbitrary number of arguments. E.g. ```fish math "sin(5,9)" ``` will return the value of sin for _9_, since this is read as "5 COMMA 9".
2018-02-11 23:02:47 +00:00
// This version was altered for inclusion in fish.
Replace muparser with tinyexpr
2018-02-10 18:46:34 +00:00
#ifndef __TINYEXPR_H__
#define __TINYEXPR_H__
#ifdef __cplusplus
extern "C" {
#endif
[tinyexpr] Add error handling This turns a bunch of ifs on their heads. We often see this pattern in te: ```c if (s->type != SOME_TYPE) { // error handling } else { // normal code } ``` Only, since we want to return the first error, we do ```c if (s->type == SOME_TYPE) { // normal code } else if (s->type != TOK_ERROR) { // Add a new error - if it already has type error // this should already be handled. } ``` One big issue is the comma operator, that means arity-1 functions can take an arbitrary number of arguments. E.g. ```fish math "sin(5,9)" ``` will return the value of sin for _9_, since this is read as "5 COMMA 9".
2018-02-11 23:02:47 +00:00
enum {
TE_ERROR_NONE = 0,
TE_ERROR_UNKNOWN_VARIABLE = 1,
TE_ERROR_MISSING_CLOSING_PAREN = 2,
TE_ERROR_MISSING_OPENING_PAREN = 3,
TE_ERROR_TOO_FEW_ARGS = 4,
TE_ERROR_TOO_MANY_ARGS = 5,
TE_ERROR_MISSING_OPERATOR = 6,
TE_ERROR_BOGUS = 7
};
typedef int te_error_type_t;
typedef struct te_error_t {
te_error_type_t type;
int position;
} te_error_t;
Replace muparser with tinyexpr
2018-02-10 18:46:34 +00:00
typedef struct te_expr {
int type;
union {double value; const double *bound; const void *function;};
void *parameters[1];
} te_expr;
enum {
TE_VARIABLE = 0,
TE_FUNCTION0 = 8, TE_FUNCTION1, TE_FUNCTION2, TE_FUNCTION3,
TE_FUNCTION4, TE_FUNCTION5, TE_FUNCTION6, TE_FUNCTION7,
TE_FLAG_PURE = 32
};
typedef struct te_variable {
const char *name;
const void *address;
int type;
void *context;
} te_variable;
/* Parses the input expression, evaluates it, and frees it. */
/* Returns NaN on error. */
[tinyexpr] Add error handling This turns a bunch of ifs on their heads. We often see this pattern in te: ```c if (s->type != SOME_TYPE) { // error handling } else { // normal code } ``` Only, since we want to return the first error, we do ```c if (s->type == SOME_TYPE) { // normal code } else if (s->type != TOK_ERROR) { // Add a new error - if it already has type error // this should already be handled. } ``` One big issue is the comma operator, that means arity-1 functions can take an arbitrary number of arguments. E.g. ```fish math "sin(5,9)" ``` will return the value of sin for _9_, since this is read as "5 COMMA 9".
2018-02-11 23:02:47 +00:00
double te_interp(const char *expression, te_error_t *error);
Replace muparser with tinyexpr
2018-02-10 18:46:34 +00:00
/* Parses the input expression and binds variables. */
/* Returns NULL on error. */
[tinyexpr] Add error handling This turns a bunch of ifs on their heads. We often see this pattern in te: ```c if (s->type != SOME_TYPE) { // error handling } else { // normal code } ``` Only, since we want to return the first error, we do ```c if (s->type == SOME_TYPE) { // normal code } else if (s->type != TOK_ERROR) { // Add a new error - if it already has type error // this should already be handled. } ``` One big issue is the comma operator, that means arity-1 functions can take an arbitrary number of arguments. E.g. ```fish math "sin(5,9)" ``` will return the value of sin for _9_, since this is read as "5 COMMA 9".
2018-02-11 23:02:47 +00:00
te_expr *te_compile(const char *expression, const te_variable *variables, int var_count, te_error_t *error);
Replace muparser with tinyexpr
2018-02-10 18:46:34 +00:00
/* Evaluates the expression. */
double te_eval(const te_expr *n);
/* Prints debugging information on the syntax tree. */
void te_print(const te_expr *n);
/* Frees the expression. */
/* This is safe to call on NULL pointers. */
void te_free(te_expr *n);
#ifdef __cplusplus
}
#endif
#endif /*__TINYEXPR_H__*/
Reference in a new issue Copy permalink