Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 25 Aug 2016 13:26:11 -0700
From:      Conrad Meyer <cem@freebsd.org>
To:        Kristof Provost <kp@freebsd.org>
Cc:        John Baldwin <jhb@freebsd.org>, Marie Helene Kvello-Aune <marieheleneka@gmail.com>,  src-committers <src-committers@freebsd.org>, svn-src-all@freebsd.org,  svn-src-head@freebsd.org
Subject:   Re: svn commit: r304815 - in head: lib lib/libifc share/examples/libifc share/mk
Message-ID:  <CAG6CVpUyK3Vcgz=EiyAFEt9-x5XG%2Bg8eyt=CORS=kMyg05G91A@mail.gmail.com>
In-Reply-To: <1A050E0F-4B9F-420A-97C6-C203B92A5F3F@FreeBSD.org>
References:  <201608251940.u7PJePv3023083@repo.freebsd.org> <23395083.lPEyYQ7ZbW@ralph.baldwin.cx> <1A050E0F-4B9F-420A-97C6-C203B92A5F3F@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Aug 25, 2016 at 1:20 PM, Kristof Provost <kp@freebsd.org> wrote:
> On 25 Aug 2016, at 22:14, John Baldwin wrote:
>> I hate even writing this mail, and it looks like the topic wasn't really
>> discussed in the review, but I think libifconfig is probably the "better"
>> name if the goal is to move most of ifconfig into it.  Certainly if a
>> developer is looking for a library that provides a programmatic interface
>> to the same operations a user does via ifconfig, libifconfig is the name
>> they will look for first.
>
> This is the right time to bring this sort of thing up. One of the reasons
> I pushed to get this in the tree in this very early state was to provoke
> exactly this sort of response. Right now the work is still in an early state
> and changing this sort of thing is still possible.
>
> The name was in fact discussed privately, and we figured libifconfig was a
> bit
> on the long side.
>
> I certainly take your point about libifc_. Does anyone else have any views
> regarding
> the naming (or other subjects)?

Hi,

I don't have anything to add, other than a "me too."

I'd second John's suggestions.  'libifconfig' for the library name is
more reasonable than libifc.  And just 'ifc_' (or even 'ifconfig_')
prefixes for public library routines is sufficient.

Thanks,
Conrad



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAG6CVpUyK3Vcgz=EiyAFEt9-x5XG%2Bg8eyt=CORS=kMyg05G91A>