Apart from this, there is new primitive: 220. If Camillo will make changes, then it will be either plugin primitive or 220. I am in favor of migrating stuff to 220 (because it is much faster) but before we will have fully functional prim220 code generator support, i think we should keep both. because then i can tell which prim i wanna use by putting either: <primitive:220 error: errorCode> or <primitive: #primitiveNativeCall module: #NativeBoostPlugin error: errorCode> and code may vary because convention is different. So, i do not see how you can safely assume that "everything which does not have primitive pragma, should use one of these" On 26 November 2012 21:42, Ciprian Teodorov <ciprian.teodorov@gmail.com> wrote:
I don't know exactly why... but I tend to agree with Igor with this one... It's not that I like copy/paste, or that the <..> pragma is sexy but it seems to me that there will be too much going on under the hood
:) yeah.. what can i say.. jumping from high level to very low level penetrating multiple layers of abstraction.. what you expected? :) But the fun part is that it demonstrates quite clearly: you can use high-level language for low-level stuff quite easy and efficient.
but ... well I hope at least that the user will see the pragma to understand that something funky is going on
-- Ciprian
On Mon, Nov 26, 2012 at 5:57 PM, Camillo Bruni <camillobruni@gmail.com> wrote:
-- Best regards, Igor Stasenko.