Meson/wren
1
0
Fork 0
forked from Mirror/wren
Code Pull Requests Activity
Files
5cd8a06fa0934c3fce7ba3393beeb970e5efa93d
wren/test/api/value.c

25 lines
464 B
C
Raw Normal View History

Add an API for storing handles to values outside of the VM. It's pretty bare bones now, but it lets you get a reference to an object from a foreign call and then return it later.
2015-08-06 22:24:15 -07:00
#include <string.h>
Simplify the API tests. Use fewer test suites with more tests in each one since there's so much boilerplate for defining an API test.
2015-08-13 09:09:27 -07:00
#include "value.h"
Add an API for storing handles to values outside of the VM. It's pretty bare bones now, but it lets you get a reference to an object from a foreign call and then return it later.
2015-08-06 22:24:15 -07:00
static WrenValue* value;
static void setValue(WrenVM* vm)
{
Start moving embedding API towards "slot" register-API. - wrenGetArgumentCount() -> wrenGetSlotCount() - wrenGetArgument___() -> wrenGetSlot___() Also, the get functions assert that the value is the right type instead of checking at runtime. This puts the onus on the caller to be safe, but maximizes performance.
2015-12-16 10:22:42 -08:00
value = wrenGetSlotValue(vm, 1);
Add an API for storing handles to values outside of the VM. It's pretty bare bones now, but it lets you get a reference to an object from a foreign call and then return it later.
2015-08-06 22:24:15 -07:00
}
static void getValue(WrenVM* vm)
{
wrenReturn___() -> wrenSlotSet___(). This turns those functions into general-purpose functions for writing raw C values into slots on the foreign call stack. Writing a return just means writing a value to slot 0.
2015-12-16 13:00:13 -08:00
wrenSetSlotValue(vm, 0, value);
Add an API for storing handles to values outside of the VM. It's pretty bare bones now, but it lets you get a reference to an object from a foreign call and then return it later.
2015-08-06 22:24:15 -07:00
wrenReleaseValue(vm, value);
}
First pass at implementing foreign classes. Most of the pieces are there: - You can declare a foreign class. - It will call your C function to provide an allocator function. - Whenever a foreign object is created, it calls the allocator. - Foreign methods can access the foreign bytes of an object. - Most of the runtime checking is in place for things like subclassing foreign classes. There is still some loose ends to tie up: - Finalizers are not called. - Some of the error-handling could be better. - The GC doesn't track how much memory a marked foreign object uses.
2015-08-15 12:07:53 -07:00
WrenForeignMethodFn valueBindMethod(const char* signature)
Add an API for storing handles to values outside of the VM. It's pretty bare bones now, but it lets you get a reference to an object from a foreign call and then return it later.
2015-08-06 22:24:15 -07:00
{
Add a benchmark to test the Wren C API. I've got some ideas on how to tweak the embedding API, but I want to see what performance impact they have first, so this adds a little benchmark that just calls a foreign method a ton of times.
2015-12-15 16:02:13 -08:00
if (strcmp(signature, "static Value.value=(_)") == 0) return setValue;
if (strcmp(signature, "static Value.value") == 0) return getValue;
Add an API for storing handles to values outside of the VM. It's pretty bare bones now, but it lets you get a reference to an object from a foreign call and then return it later.
2015-08-06 22:24:15 -07:00
return NULL;
}
Copy Permalink