[Top][All Lists]

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

[Octave-bug-tracker] [bug #48793] no need for OCTAVE_LOCAL_BUFFER anymor

From: John W. Eaton
Subject: [Octave-bug-tracker] [bug #48793] no need for OCTAVE_LOCAL_BUFFER anymore
Date: Thu, 20 Jul 2017 17:14:23 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0

Follow-up Comment #10, bug #48793 (project octave):

Thanks for looking at this.  I suspect the difference in performance could be
that getting a pointer from the chunk_buffer is a lot faster than calling new
to allocate memory.  But I'm not sure it's worth the extra complexity.  It's
good to see a reduction of around 300 lines without really losing anything.

Did you mean to leave the "assert (0)" in the version of the
OCTAVE_LOCAL_BUFFER macro that is supposed to be used with C++14 and later? 
For consistency, it should probably also not end with a semicolon.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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