Andrew Whitworth wrote:
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.
I tend to disagree with myself as well (just because I was involved in
those branches). But question is who wins - common sense or PARROT_EXPORT?
--
Bacek
_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev
