octave-bug-tracker
[Top][All Lists]
Advanced

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

[Octave-bug-tracker] [bug #40534] Fix null pointer access in octave_fcn_


From: John W. Eaton
Subject: [Octave-bug-tracker] [bug #40534] Fix null pointer access in octave_fcn_binder::maybe_binder
Date: Mon, 11 Nov 2013 06:57:20 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130810 Firefox/17.0 Iceweasel/17.0.8

Follow-up Comment #3, bug #40534 (project octave):

We also avoid using NULL in C++ code.  I checked in another changeset to fix
that in ov-fcn-handle.cc and a few other files.

Unless there is some ambiguity, the filenames in the log entries don't need to
include the full directory name.  But we normally do include the class name as
part of the function name.  And there should be a space between the file name
and the function name. So you should write


* ov-fcn-handle.cc (octave_fcn_binder::maybe_binder): Avoid possible null
pointer access.


instead of


* libinterp/octave-value/ov-fcn-handle.cc(maybe_binder): ...


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?40534>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

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