On Sun, May 10, 2009 at 8:21 AM, Vasily Chekalkin <[email protected]> wrote: > Looks like latest merges of branches related to VTABLE refactoring have to > be reverted. > > Main point - we break API compatibility without proper deprecation notice. > Previously we used to export all generated C-functions, now we don't. It > cause problems with language implementations which call those functions > directly. See #651 for lua as very clear explanations.
I disagree. We've always suggest that developers use the VTABLE_* macros to access vtable functionality instead of calling the functions directly. People should not be surprised when an internal interface, that we always said not to use directly, disappears. We shouldn't need a deprecation cycle for this, these are Parrot internals (never intended to be user-facing, even if they were mistakenly generated as PARROT_EXPORT) and people who have been using these functions directly from external projects were doing it wrong in the first place. --Andrew Whitworth _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
