From: Guillermo <gdiazhartusch@gmail.com>
To: supervision@list.skarnet.org
Subject: Re: G++ warnings for set-control-group-knob from nosh-1.37
Date: Sun, 11 Mar 2018 23:33:00 -0300 [thread overview]
Message-ID: <CADQ2Nw8N8QeFYS9u03HqhzKjJ2H2MzigS2msp84kGA9wpc7isg@mail.gmail.com> (raw)
In-Reply-To: <27dc6882-1c58-e64e-afd4-d08c6b13f8ee@NTLWorld.COM>
2018-03-11 20:57 GMT-03:00 Jonathan de Boyne Pollard:
>
> The macro generates no warning in the GNU C library in Debian 9, but I
> should have caught that overload that was not passing by reference. It is
> fixed now, thank you. The in-development source archive for 1.38 is in the
> usual place.
Yes, both G++ warnings are gone now. BTW, the removal of the macros
from <sys/types.h> has already been committed, so it looks like it is
going to happen for GNU libc version 2.28:
* https://sourceware.org/git/?p=glibc.git;a=commit;h=e16deca62e16f645213dffd4ecd1153c37765f17
However, a new warning has appeared:
In file included from set-control-group-knob.cpp:23:0:
popt.h:85:16: warning: 'virtual bool
popt::table_definition::execute(popt::processor&, char, const char*)'
was hidden [-Woverloaded-virtual]
virtual bool execute(processor &, char c, const char * s);
^~~~~~~
popt.h:100:16: warning: by 'popt::top_table_definition::execute'
[-Woverloaded-virtual]
virtual bool execute(processor &, const char * s);
^~~~~~~
I believe this is because the 1.38 development version dropped a
'using table_definition::execute;' declaration from the definition of
class popt::top_table_definition that was present in 1.37, so the
three parameter version of popt::table_definition::execute() would now
be hidden. I only did a quick 'redo set-control-group-knob.o' test, so
I'm not sure if it is important or if it affects anything, though.
Thanks,
G.
next prev parent reply other threads:[~2018-03-12 2:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-11 15:06 Guillermo
2018-03-11 23:57 ` Jonathan de Boyne Pollard
2018-03-12 2:33 ` Guillermo [this message]
2018-03-17 13:33 ` uschedule service bundles supplied with the nosh toolset Jonathan de Boyne Pollard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADQ2Nw8N8QeFYS9u03HqhzKjJ2H2MzigS2msp84kGA9wpc7isg@mail.gmail.com \
--to=gdiazhartusch@gmail.com \
--cc=supervision@list.skarnet.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).