|
From: Bob D. <bd...@si...> - 2005-06-05 14:24:08
|
Hi,
Patch looks correct. Right now I only maintain the PHP bindings by
hand.
Right now there are a few things the Python(And other SWIG Interfaces)
interface doesn't have, would you be willing to do any of these? I have
manually done these in PHP
1) Array Data Source: Use a 2D array as a data source
2) Signals/Callbacks: Right now in PHP we can attach to events in the
RLIB engine and it will call back to a PHP function to do whatever...
3) "m.xxx" environment variables. In PHP it looks at the global symbol
table for xxx and gets the value it needs
4) Custom functions. Add custom functions to the engine that RLIB does
not provide. So in PHP:
rlib_add_function($rlib, "test", "test_function", 2);
function mike_roth($a, $b) {
return "pancakes are yummier then $a and $b";
}
Then in the RLIB XML:
you would do: ..... value="test('bacon', 'eggs')"
======
Obviously if you did these things I would start making the bindings by
hand in the future (Normally it's a copy and paste job)
Also, just out of curiosity what are you trying to use RLIB for?
- Bob
|