Sebastian Benoit wrote:
> > OK. Another option is to use __func__ which is always correct.
>
> Please definatly use __func__. With that ok benno too.
I like __func__ where it makes sense, but often developers consider
"i've shown an obscurely named function that i know" to be a solved
problem,
Claudio Jeker(cje...@diehard.n-r-g.com) on 2019.11.09 15:32:39 +0100:
> On Sat, Nov 09, 2019 at 03:27:31PM +0100, Denis Fondras wrote:
> > Fix function name in error message.
> >
> > Index: kroute.c
> > ===
> > RCS file:
On Sat, Nov 09, 2019 at 03:27:31PM +0100, Denis Fondras wrote:
> Fix function name in error message.
>
> Index: kroute.c
> ===
> RCS file: /cvs/src/usr.sbin/ospfd/kroute.c,v
> retrieving revision 1.112
> diff -u -p -r1.112 kroute.c
>
Fix function name in error message.
Index: kroute.c
===
RCS file: /cvs/src/usr.sbin/ospfd/kroute.c,v
retrieving revision 1.112
diff -u -p -r1.112 kroute.c
--- kroute.c28 Dec 2018 19:25:10 - 1.112
+++ kroute.c9 Nov
