extism

github/extism

Fork 0

mirror of https://github.com/extism/extism.git synced 2026-04-23 03:00:11 -04:00

Commit Graph

Author	SHA1	Message	Date
zach	4a49408045	fix: handle large allocations (missing commits) (#14 )	2022-09-13 00:17:05 -06:00
Benjamin Eckel	ffa01403a3	feat(ruby-sdk): create Extism module / namespace (#5 ) I noticed when calling set_log_file that it's on the top-level namespace. And so is the rest of the gem. It's not a good idea to do this as it pollutes the user's application. Best practice is to wrap all code in a module which by convention is the gem name. I was also getting `Uninitialized constant FFI:NIL` and in the set_log_file method and I could not tell why it was needed. I changed it to a regular ruby nil. If it's needed for some reason I'll change it back or move to another PR.	2022-09-04 17:05:10 -06:00
Steve Manuel	e27fae9193	v0.0.1 alpha Co-authored-by: Zach Shipko <zach@dylib.so>	2022-08-25 14:36:47 -06:00

Author

SHA1

Message

Date

zach

4a49408045

fix: handle large allocations (missing commits) (#14 )

2022-09-13 00:17:05 -06:00

Benjamin Eckel

ffa01403a3

feat(ruby-sdk): create Extism module / namespace (#5 )

I noticed when calling set_log_file that it's on the top-level namespace.
And so is the rest of the gem. It's not a good idea to do this as it
pollutes the user's application. Best practice is to wrap all code in a
module which by convention is the gem name.

I was also getting `Uninitialized constant FFI:NIL` and in the
set_log_file method and I could not tell why it was needed. I changed it
to a regular ruby nil. If it's needed for some reason I'll change it
back or move to another PR.

2022-09-04 17:05:10 -06:00

Steve Manuel

e27fae9193

v0.0.1 alpha

Co-authored-by: Zach Shipko <zach@dylib.so>

2022-08-25 14:36:47 -06:00

3 Commits