[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #65532] '[=]' is deprecated
From: |
Jeffrey Cliff |
Subject: |
[Octave-bug-tracker] [bug #65532] '[=]' is deprecated |
Date: |
Fri, 29 Mar 2024 02:18:04 -0400 (EDT) |
URL:
<https://savannah.gnu.org/bugs/?65532>
Summary: '[=]' is deprecated
Group: GNU Octave
Submitter: themusicgod1
Submitted: Fri 29 Mar 2024 01:18:03 AM CDT
Category: Octave Package
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: Unexpected Error or Warning
Status: None
Assigned to: None
Originator Name:
Originator Email:
Open/Closed: Open
Release: 8.4.0
Discussion Lock: Any
Operating System: GNU/Linux
Fixed Release: None
Planned Release: None
_______________________________________________________
Follow-up Comments:
-------------------------------------------------------
Date: Fri 29 Mar 2024 01:18:03 AM CDT By: Jeffrey Cliff <themusicgod1>
while compiling ( with -std=gnu++20 ) , over and over while building, this
warning comes up:
./liboctave/array/Range.h: In lambda function:
./liboctave/array/Range.h:276:22: warning: implicit capture of 'this' via
'[=]' is deprecated in C++20 [-Wdeprecated]
276 | idx.loop (n, [=, &array] (octave_idx_type i)
| ^
./liboctave/array/Range.h:276:22: note: add explicit 'this' or '*this'
capture
https://isocpp.org/files/papers/p0806r2.html suggests that 'this' should
explicitly be invoked here (though none of the examples have a second
argument)
and, granted, the easy way to make this go away is to just not bother with
-std=gnu++20 but still: use of deprecated C++ is a flaw whether it's valid or
not.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?65532>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #65532] '[=]' is deprecated,
Jeffrey Cliff <=