On 2013-11-16 00:10, Thomas Mayer wrote:
> So, for objects that need a special character converted to hex, the
> setup function must be called setup_, while for other objects
> the setup function must be called _setup.
>
> This is kind of confusing.
yes, but it's the way it is.
the "_setup()" na
Hi,
On 15.11.2013 19:28, Thomas Mayer wrote:
> On 15.11.2013 10:43, IOhannes m zmölnig wrote:
>> i'm not sure what you want to acchieve.
>
> I want to achieve a common naming convention for the setup function of
> all objects in my library, currently some have the name of
> _setup, some setup_.
>
Hi,
On 15.11.2013 10:43, IOhannes m zmölnig wrote:
> i'm not sure what you want to acchieve.
I want to achieve a common naming convention for the setup function of
all objects in my library, currently some have the name of
_setup, some setup_.
> it seems that you are creating an object [json-enc
On 2013-11-14 23:44, Thomas Mayer wrote:
> Hello,
>
> I am currently documenting and refactoring the code of PuREST JSON to be
> consistent, but I seem to be unable to rename setup function from
> setup_json0x2dencode to json_encode_setup, as after renaming, I get the
> following error:
>
> error
Hello,
I am currently documenting and refactoring the code of PuREST JSON to be
consistent, but I seem to be unable to rename setup function from
setup_json0x2dencode to json_encode_setup, as after renaming, I get the
following error:
error: load_object: Symbol "setup_json0x2dencode" not found
j
