From 9347c5c61ad461a83f6d7ee81d3dfd9afaf0845a Mon Sep 17 00:00:00 2001 From: Will Speak Date: Wed, 3 Oct 2018 07:39:26 +0100 Subject: [PATCH] Update Call to `WrenInterpret` in Docs Fixes #599 by updating the arguments to WrenInterpret to match the new API. --- doc/site/embedding/index.markdown | 4 +++- doc/site/embedding/storing-c-data.markdown | 2 +- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/doc/site/embedding/index.markdown b/doc/site/embedding/index.markdown index ee566896..35edd57b 100644 --- a/doc/site/embedding/index.markdown +++ b/doc/site/embedding/index.markdown @@ -131,7 +131,9 @@ VM, waiting to run some code! You execute a string of Wren source code like so: :::c - WrenInterpretResult result = wrenInterpret(vm, + WrenInterpretResult result = wrenInterpret( + vm, + "my_module", "System.print(\"I am running in a VM!\")"); The string is a series of one or more statements separated by newlines. Wren diff --git a/doc/site/embedding/storing-c-data.markdown b/doc/site/embedding/storing-c-data.markdown index 4ff6422c..0c96fa79 100644 --- a/doc/site/embedding/storing-c-data.markdown +++ b/doc/site/embedding/storing-c-data.markdown @@ -207,7 +207,7 @@ Over in the host, first we'll set up the VM: config.bindForeignMethodFn = bindForeignMethod; WrenVM* vm = wrenNewVM(&config); - wrenInterpret(vm, "some code..."); + wrenInterpret(vm, "my_module", "some code..."); return 0; }