Escape certain reserved terms when building member functions

[Shaptic]

Closes #153.

Note: I'm still testing the end-to-end with js-stellar-base.

[tsachiherman]

I think that at some point we'd need to extend that to all the js reserved words, but at this point in time, the fix looks as if it would produce a good workaround.

[Shaptic]

@tsachiherman it's not that set is reserved by JS (it isn't), it's that set is a method used internally by js-xdr to actually build the structures. Thus, having an actual member named set overwrites that, making it impossible to, well, actually set fields.

[tsachiherman]

@tsachiherman it's not that set is reserved by JS (it isn't), it's that set is a method used internally by js-xdr to actually build the structures. Thus, having an actual member named set overwrites that, making it impossible to, well, actually set fields.

so, you're saying that theoretically it would be a parameter provided to the xdrgen to rename a certain names ?

[Shaptic]

@tsachiherman we can expand the list in member_name as needed of course, now, but I don't think it needs to be configurable if that's what you're implying

I'm just saying that the root cause is more-so that set is "reserved" by js-xdr internally rather than by the language itself.