> Message: 5 > Date: Mon, 22 Sep 2014 15:17:36 +0100 > From: Phil Rosenberg <philip_rosenb...@yahoo.com> > Subject: [Plplot-devel] Exit calls and memory management > To: PLplot development list <Plplot-devel@lists.sourceforge.net> > Message-ID: <218078.55503...@smtp115.mail.ir2.yahoo.com> > Content-Type: text/plain; charset="windows-1252" > > This one is mostly directed at Alan but probably others will be interested > and may have comments. Git might also be a big help here, but I'm not sure > how it will work so advice from all appreciated. > > I have been trying to improve memory management in plplot as part of my > attempt to try to remove exit calls. To do this I am removing raw pointer > arrays and replacing them with a struct which will give us more object > oriented access to memory allocation. I think this will be a generally good > thing as the struct can have function pointers which will allow trivial > resizing and adding elements. It will also be extendible, to allow further > functionality similar to std::vector if we want. Arrays will also know their > own size. > > However the cost is that arrays in the plstream will all become structs so > will need accessing by somearray.mem[index] or maybe > somearray.getMem()[index] rather than somearray[index]. This has the > potential to break some or all the drivers. Although the fixes might be > trivial, I don't have easy access to all the drivers on my windows machine. > > I'm therefore looking for a suggestion of how to proceed. I can transfer > stuff to my Linux machine, but I'm not sure how best to do that with git. I > could create a fork on github so other developers can contribute, but if I > create a public fork then we should merge that into the master branch rather > than rebase it which I think is not compliant with our current workflow.
I think creating a branch on github (or some other public repository) is the only way that you can proceed if you want others to see what you are doing. Though not perhaps ideal, you should be able to rebase master off a public branch. If you are interested, Hez or I could add you to the PLplot organization on github. Then you could push your branch there. We haven't done anything with it yet, so you'll have to create a the repository first. https://github.com/PLplot -Hazen ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
