You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Builder’s custom init function provides mechanism to provide custom allocator to flatcc builder.
The flatcc_builder_alloc_fun contains alloc and free calls. This allows multiple flatcc builders in a project to have different alloc and free functions. This just requires a new function to be sent during init.
Any reason why the same was functionality was not extended to flatcc_builder_emit_fun?
Theoretically, flatcc_builder_custom_init and emitter.c can be modified to make it behave similar to alloc_fun. But does this cause any known issues?
Similarly refmap and json_printer don’t expose this functionality.
The text was updated successfully, but these errors were encountered:
Builder’s custom init function provides mechanism to provide custom allocator to flatcc builder.
The flatcc_builder_alloc_fun contains alloc and free calls. This allows multiple flatcc builders in a project to have different alloc and free functions. This just requires a new function to be sent during init.
Any reason why the same was functionality was not extended to flatcc_builder_emit_fun?
Theoretically, flatcc_builder_custom_init and emitter.c can be modified to make it behave similar to alloc_fun. But does this cause any known issues?
Similarly refmap and json_printer don’t expose this functionality.
The text was updated successfully, but these errors were encountered: