help-octave
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: overloading the global new/delete operator in octave


From: John W. Eaton
Subject: Re: overloading the global new/delete operator in octave
Date: Fri, 7 Aug 2009 13:57:41 -0400

On  3-Aug-2009, Soeren Sonnenburg wrote:

| On Mon, 2009-08-03 at 00:13 -0700, Sergei Steshenko wrote: 
| > 
| > 
| > --- On Sun, 8/2/09, Soeren Sonnenburg <address@hidden> wrote:
| > 
| > > From: Soeren Sonnenburg <address@hidden>
| > > Subject: overloading the global new/delete operator in octave
| > > To: "Octave users list" <address@hidden>
| > > Date: Sunday, August 2, 2009, 11:45 AM
| > > Dear all,
| > > 
| > > I am a bit puzzled why my overloaded global new[] operator
| > > does not
| > > become effective when building a octave extension (it works
| > > with
| > > python/matlab though)...
| [...] 
| > It's probably a (wrong) long shot, but try
| > 
| > fprintf(stderr, "test\n");
| > 
| > - you know, (un)buffered output. Experimentally stdout sometimes takes a
| > lot of time/output to get flushed.
| 
| That was not the cause (and I still don't know what could potentially
| cause it). However, I managed to create a an isolated toy example which
| works just fine :-) So there could be a problem related to interactions
| between the two libraries I link against (which in fact implement this
| overloading...). Anyway working isolated example follows:

If you post a complete example that demonstrates the problem, maybe
someone can help.  I'm not sure how we are supposed to help debug a
problem when you post an example that doesn't show the problem.  :-)

jwe


reply via email to

[Prev in Thread] Current Thread [Next in Thread]