@lists.sourceforge.net; Hezekiah M.
Carty h...@0ok.org
Sent: Monday, 22 September 2014, 23:00
Subject: Re: [Plplot-devel] Exit calls and memory management
On 2014-09-22 16:41-0400 Hazen Babcock wrote:
On 9/22/2014 3:37 PM, Alan W. Irwin wrote:
On 2014-09-22 12:08-0400 Hazen Babcock wrote
On 2014-09-23 03:30-0700 phil rosenberg wrote:
@Hazen and Alan
I think an email went AWOL from Hazen somewhere, but from Alan's reply I
guess it probably said that we should not be rebasing public branches. I must
confess that I think almost everything I have read about rebasing says do not
Hi, Alan,
On Sep 22, 2014, at 12:37 PM, Alan W. Irwin wrote:
You are much more experienced with git than me. However, I thought
that rebasing a public branch was always a bad idea for the reasons I
mentioned concerning disappearing commits. I am positive a number of
resources I read when
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
Unless the memory calls have changed, the raw pointers was something I
implemented 5+ years ago when I submitted a patch to transition away from
temporary files.
The design goal I had in mind was speed, to keep the implementation portable,
and to make the memory buffers agnostic to the data.
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
On 2014-09-22 15:17+0100 Phil Rosenberg wrote:
However the cost [of this change] 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
Subject: Re: [Plplot-devel] Exit calls and memory management
Unless the memory calls have changed, the raw pointers was something I
implemented 5+ years ago when I submitted a patch to transition away from
temporary files.
The design goal I had in mind was speed, to keep the implementation
On 2014-09-22 12:08-0400 Hazen Babcock wrote:
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.
Hi Hazen:
On 9/22/2014 3:37 PM, Alan W. Irwin wrote:
On 2014-09-22 12:08-0400 Hazen Babcock wrote:
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
Phil,
This is a laudible plan, however fundamentally it won't remove the exit
calls from plplot. The reason is that memory allocation can fail. We
always need to check this and fail graceful, returning an error to the
calling program and letting it decide how to procede. However we do the
On 2014-09-22 16:41-0400 Hazen Babcock wrote:
On 9/22/2014 3:37 PM, Alan W. Irwin wrote:
On 2014-09-22 12:08-0400 Hazen Babcock wrote:
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.
12 matches
Mail list logo
