apfl/src/strings.h

#ifndef APFL_STRINGS_H
#define APFL_STRINGS_H

#ifdef __cplusplus
extern "C" {
#endif

#include "apfl.h"
#include "gc.h"

struct apfl_string *apfl_string_move_into_new_gc_string(struct gc *gc, struct apfl_string *in);
struct apfl_string *apfl_string_copy_to_new_gc_string(struct gc *gc, struct apfl_string_view sv);

#ifdef __cplusplus
}
#endif

#endif
Ditch that weird internal.h header 2022-04-22 21:17:28 +00:00			`#ifndef APFL_STRINGS_H`
			`#define APFL_STRINGS_H`
Initial commit 2021-12-10 20:22:16 +00:00
			`#ifdef __cplusplus`
			`extern "C" {`
			`#endif`

Ditch that weird internal.h header 2022-04-22 21:17:28 +00:00			`#include "apfl.h"`
Push formatted parser error on stack during evaluation This way we can see the parse errors again in evaluation mode Not fully fleshed out yet: We simply use apfl_debug_print_val to dump the top of the stack (the formatted error) to stderr but don't nicely handle if there is nothing on the stack (apfl_debug_print_val will print a rather cryptic "stack index invalid" error). Also the whole dance we need to do to put the formatted error onto the stack feels rather awkward (there should probably a function for this) and we also should probably try to push an error description on the stack in case this moving-string-to-stack business fails. Now "only" all other errors need to be put on the stack as a string :) 2022-04-21 20:40:27 +00:00			`#include "gc.h"`

			`struct apfl_string apfl_string_move_into_new_gc_string(struct gc gc, struct apfl_string *in);`
Define globals in apfl itself We're now first building a standalone bytecode compiler `apflc` that will compile `globals.apfl` into bytecode and write it out as a C source file. When initializing a new context, that embedded bytecode will then get evaluated and the global scope will be populated from the dictionary returned by that bytecode. 2023-03-05 21:55:20 +00:00			`struct apfl_string apfl_string_copy_to_new_gc_string(struct gc gc, struct apfl_string_view sv);`
Push formatted parser error on stack during evaluation This way we can see the parse errors again in evaluation mode Not fully fleshed out yet: We simply use apfl_debug_print_val to dump the top of the stack (the formatted error) to stderr but don't nicely handle if there is nothing on the stack (apfl_debug_print_val will print a rather cryptic "stack index invalid" error). Also the whole dance we need to do to put the formatted error onto the stack feels rather awkward (there should probably a function for this) and we also should probably try to push an error description on the stack in case this moving-string-to-stack business fails. Now "only" all other errors need to be put on the stack as a string :) 2022-04-21 20:40:27 +00:00
Initial commit 2021-12-10 20:22:16 +00:00			`#ifdef __cplusplus`
			`}`
			`#endif`

			`#endif`