On 17 May 2017, at 15:11, Cyril Ferlicot D. <cyril.ferlicot@gmail.com> wrote:
On 17/05/2017 14:55, Sven Van Caekenberghe wrote:
The use of #stonAllInstVarNames works in limiting what you write out (there is even a unit test based on STONTestUser3).
But you seem to want to do something else, you want to write the others ones out in a different way.
What I tried to explain is that that is generally not needed, if you customise the value of #variableToCustomise (that is one level deeper). This is what I did in the example.
Since you can't or won't explain your use case better, I really can't help, can I ?
I don't really have the time right now but later I'll try to write a simple example.
OK. But don't go too far in writing actual code. I want to understand the use case at a high level (like how you started), then I can try to find how/if STON can do what you want. Right now, you are already too deep into a possible solution.
-- Cyril Ferlicot https://ferlicot.fr
http://www.synectique.eu 2 rue Jacques Prévert 01, 59650 Villeneuve d'ascq France