On Fri, May 13, 2011 at 09:53:10PM -0400, Peter Lobsinger wrote: > On Fri, May 13, 2011 at 3:58 PM, Patrick R. Michaud <[email protected]> > wrote: > > I also notice that according to api.yaml the UnManagedStruct type > > is deprecated and eligible for removal in 3.4 (i.e., "now"). > > Zavolaj uses that also, so in order to avoid another "surprise" > > we need details on the upgrade path for that as well. > > TT #2035 already gives an upgrade path.
I vehemently disagree with the notion of "upgrade path" implied by this response and the ticket. To me, an "upgrade path" is more than saying "try using one of these other undocumented classes over here". An "upgrade path" gives me (a user) sufficient information that I can take my existing code and make it work in the new environment without having to ask basic questions or search lots of Parrot C source code to try to figure things out. I should be able to find examples of how the code is to be used. Based on reading the #2035 ticket, I have no clue what a Ptr, PtrBuf, PtrObj, or StructView PMC might be, what they can do, or how to use them. It provides me no links or suggestions where I might look for this information. Doing a search through the Parrot sources reveals little documentation on any of these classes, unless I want to try to decipher the C code that implements them. AFAICT there is exactly one test that makes use of StructView (in t/pmc/nci.t), and in that test I have no clue what the constants .DATATYPE_STRUCT or .DATATYPE_PIR are intended to represent. Unlike UnManagedStruct, there are no existing examples, PDDs, or library code that I can look to for an idea of how these new classes might be used. (UnManagedStruct has all of these.) A search for "StructView" in trac.parrot.org only brings up a few tickets; the #2035 ticket and a few others that describe problems with StructView. A search for "PtrObj" only brings up the #2035 ticket. I'm sorry, but this notion of "upgrade path" is not at all the sense I get from reading the relevant Parrot support policy documents. If I'm wrong about this, please tell me now so Rakudo can decide to simply pick a current version of Parrot and stick with it while other Parrot users pay the associated upgrade penalties. Pm _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
