P.S. I had obviously completely forgotten the thread on this very subject last January with a subject line of
D language bindings - future directions but I have found that thread now. The executive summary was we all more or less agreed it was time to move to D2 (although nothing has been done since.) Andrew and I were concerned about the method that should be used to generate and maintain the D2 bindings. We both liked swig for this task, but Werner's take was "I think the major problems are not the bindings, which were rather easy to create (and maintain), but porting our samples to D2 (which should be easy) and Tango (which is more work)." I am willing to trust Werner's opinion that the simplest way to convert the bindings to D2 and maintain them afterwards is via hand editing. In fact, I have already started using that method with my cast changes, and it does appear such simple changes will deal with the large majority of the build errors with the bindings. Furthermore, from what he said the transition to D2 should also be simple for the examples since it turns out we don't have to worry about Tango since phobos (via the libgphobos2 library) apparently works fine with D2. So assuming we are all now agreed that hand-editing is the way to go for the bindings, shall I go ahead and commit my Language support changes as well as the simple cast changes I can find to whittle down the error messages for the bindings? These changes would mean D would have to be disabled until the work is finished by your efforts (since I am not capable of finishing it myself). So let me know whether you think I should commit (including the disabling of D). Alan __________________________ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); the Time Ephemerides project (timeephem.sf.net); PLplot scientific plotting software package (plplot.sf.net); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
