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
We are using mattn/go-sqlite3 in stackql/stackql; we need to add custom extension functions specific to our program. We wouldn't expect these to be committed to this project, but we want an easy, repeatable, automated method to add our functions in a fork via a make target (like make amalgamate). We believe other developers would benefit from this capability as well.
Proposal
Inline documentation is proposed to facilitate developers' addition of custom extension functions. My approach would be to add comments within the sqlite3-binding.c file that serve as placeholders for adding custom extension functions. This would help external developers understand where to include their extension functions without requiring the maintainers of matte/go-sqlite3 to verify, test, or maintain those external functions.
Proposed Changes
1. Forward Declarations
// CUSTOM_EXTENSIONS// 1. Add custom extension initializer function declarations here...// End CUSTOM_EXTENSIONS
2. Extension Initializer Array
// CUSTOM_EXTENSIONS// 2. Include custom extension initializer functions here...// End CUSTOM_EXTENSIONS
These comments will provide clear guidance to developers looking to add custom extensions, helping them to understand the appropriate sections in the sqlite3-binding.c file where they should include their code.
Request
I would like to open a pull request to add these comments and would appreciate any feedback or suggestions.
The text was updated successfully, but these errors were encountered:
Background
We are using
mattn/go-sqlite3
instackql/stackql
; we need to add custom extension functions specific to our program. We wouldn't expect these to be committed to this project, but we want an easy, repeatable, automated method to add our functions in a fork via amake
target (likemake amalgamate
). We believe other developers would benefit from this capability as well.Proposal
Inline documentation is proposed to facilitate developers' addition of custom extension functions. My approach would be to add comments within the
sqlite3-binding.c
file that serve as placeholders for adding custom extension functions. This would help external developers understand where to include their extension functions without requiring the maintainers ofmatte/go-sqlite3
to verify, test, or maintain those external functions.Proposed Changes
1. Forward Declarations
2. Extension Initializer Array
3. Extension Initializer Functions
Benefit
These comments will provide clear guidance to developers looking to add custom extensions, helping them to understand the appropriate sections in the
sqlite3-binding.c
file where they should include their code.Request
I would like to open a pull request to add these comments and would appreciate any feedback or suggestions.
The text was updated successfully, but these errors were encountered: