> I'm not trying to be facetious, I really do want to know for future > reference what people expect to happen when we make a C-level API > change like this. There comes a point in the process when we need to > stop offering the old function and start expecting people to be using > the new version. Knowing when that point should be is going to be > extremely important for us in the coming months, so we should figure > it out now.
The problem is that we have several eligible deprecation items which lacks replacement. We shouldn't do that, eligibility should be set after the replacement is on place. I think we agreed on that at some #ps, but there are many deprecations created before that. > The function in question has been renamed to > Parrot_hll_get_ctx_HLL_namespace, for reference. We should have a list of that renames in the Parrot Deprecations page on the wiki. -- Salu2 _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
