Chris: not sure, but searching with svTHINKFIRST gives nothing, and I saw nothing by glancing over the perlguts page.
David: good if PDL does ok copying in all its many places and everyone have stuck to the interface .. but many Inline/XS people will have done string copying in Perl, expecting a new copy. I can't tell who it bites, but the argument is there ought to be an environment variable to keep the old way, to keep existing code working. Niels On Fri, 2014-09-19 at 08:23 -0400, Chris Marshall wrote: > I'm concerned as well given that the types of problems > described could cause real difficulty with working with > PDL data from the perl level since it seems to cause > spooky action at a distance that is different than all > previous expectations. > > The use case that comes to mind is doing large data > IO, say a stream of bytes, and then "casting" that into > the desired piddle "in place" without a copy being > forced. > > I haven't looked at 5.20.1 docs yet but are there some > guidelines for how to avoid these types of problems > that will work in a back-compatible fashion? > > --Chris _______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
