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
This RFC proposes the addition of an export keyword to specify that functions for a class should be generated even if they are not used directly in the Pony program that is being compiled. Additionally, wrapper functions for these functions that conform to the C ABI will be generated, along with a .h file with the appropriate function signatures so that the functions can be easily used from a C program. The .h file will only be generated if the program is compiled with the --export compiler flag.
Note that in addition to code, this RFC has test and documentation requirements that have to be done in order to merge. Full RFC details are at:
Yeah. I already have most of it implemented, but I'll move it to in progress when I start the process of whipping it into shape (tests, documentation, etc).
This RFC proposes the addition of an
export
keyword to specify that functions for a class should be generated even if they are not used directly in the Pony program that is being compiled. Additionally, wrapper functions for these functions that conform to the C ABI will be generated, along with a .h file with the appropriate function signatures so that the functions can be easily used from a C program. The .h file will only be generated if the program is compiled with the--export
compiler flag.Note that in addition to code, this RFC has test and documentation requirements that have to be done in order to merge. Full RFC details are at:
https://github.com/ponylang/rfcs/blob/master/text/0018-export.md
The text was updated successfully, but these errors were encountered: