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

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

[Octave-bug-tracker] [bug #51565] Use nullptr rather than 0 in C++11 cod


From: Rik
Subject: [Octave-bug-tracker] [bug #51565] Use nullptr rather than 0 in C++11 code
Date: Thu, 27 Jul 2017 11:50:05 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:54.0) Gecko/20100101 Firefox/54.0

Update of bug #51565 (project octave):

                  Status:             In Progress => Fixed                  
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #9:

Finally, this should be it.  Last changeset for nullptr checked in here
(http://hg.savannah.gnu.org/hgweb/octave/rev/771310737137).

There still may be instances that have not been discovered because of the way
we are using the compiler to check.  I noticed that there were some spots in
the code with #if defined / #else blocks where both blocks had function calls
that were making use of 0 rather than nullptr.  GCC only reports on the code
that was actually compiled so one of the branches was always being missed.  I
changed the code if I noticed the block, but I might have overlooked some.

Anyways, marking as fixed and closing report.

    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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