On 28 February 2010 07:54, Andreas Raab <andreas.raab@gmx.de> wrote:
Folks -
Back to lurking for now,
wait.. i'd really like to have eventually <apicall: 'Win32HBrush CreateSolidBrush (ulong)' module: 'gdi32.dll'> instead of: <apicall: Win32HBrush 'CreateSolidBrush' (ulong) module: 'gdi32.dll'> so, pragma syntax will be consistent. Yes, backwards compatibility hurts. Yes everything has its costs, but.. do you willing to reopen this topic again (after 4 years passed) towards making FFI pragmas pluggable into parser/compiler? By pluggable i mean that by loading next-gen FFI package, there will be no need to patch/add not a single method in parser/compiler. I think its quite easy to write some code which helps with transition automation. I imagine a following process: - write a new FFI-Legacy package, which supports transition to new format then user: - loads this package, before loading any code which using FFI - load any code which using FFI , during which it should be automatically converted to new pragma format(s) - save converted code - user now free to unload FFI-Legacy and use new pragma syntax.
 - Andreas
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Best regards, Igor Stasenko AKA sig.