Returning a Rebol TRIPWIRE (TRASH!)

[hostilefork]

A few years down the road... there's another answer: return can just return code to run.

What Should Returning a String From a Native Do?

I've raved about how cool rebFunction() is... though it may seem like mundane C interop, it's not. It's quite novel. But to recap, a trivial example: const char* Add_1000_Spec = "[ \ -{Adds 1000 to whatever you pass in}- \ return: [integer!] \ x [integer!] \ ]"; Bounce Add_1000_Impl(Context* binding) { int x = rebUnboxInteger("x"); int bigger = x + 1000; return rebInteger(bigger); } Value* action = rebFunction(Add_1000_Spec, &Add_1000_Impl); So here you see us return…

So you can say return "x + y"; and it will run, looking up those variables in the current "scope" (e.g. it can find the native's arguments, or definitions in an extension's MODULE!)

If you want to return VOID, you can say return "~"; or return "()"

And so if you want a TRASH! like a "tripwire" you can just say return "~<?>~";