On 26 November 2012 01:35, Camillo Bruni <[email protected]> wrote: > > On 2012-11-25, at 21:28, Igor Stasenko <[email protected]> wrote: > >> On 25 November 2012 23:11, Camillo Bruni <[email protected]> wrote: >>> And don't forget to make the primitive declaration automatic, nobody can >>> remember that cryptic string :) >>> >> once we'll have opal on board.. not before that. i don't want to hack >> current compiler. > > no need to hack the compiler > - on the first call check if there is the primitive > - if there is none, check if the method contains any other primitive > - if not, add the primitive to the second line of the method sources > - recompile the method with the same primitive > - call that method again > > so you got a solution that works already now, I don't see what opal will > add you here? >
what i was wanted to say that instead of using long cryptic string, with opal i could use a very simple pragma , like <native>. modifying source code is a slippery road, with a lot of pitfalls down the sides.... i am one, who thinks that automatic tools should not interfere with what author(s) wanted to say. i prefer to leave source as it was written, but we can instruct the compiler to insert primitive once we discover that it is not there but without modifying source code. -- Best regards, Igor Stasenko.
