Re: Win32 Network Adapter module naming

Win32::Network::Adapter - getting un-useful-ly long just to be overly descriptive

Disagree. It's hard to imagine a name being "overly" descriptive ... the more specific it is, the better. Also, the closer it is to natural language, for searching to find it when you don't know what it's called.

Also, I don't think this example is anywhere close to being un-usefully long. You only have to write it once after all.

As to the actual name, I am not qualified to say, but hippo's suggestion as well as this one -- even Win32::Network::Adapter::Info if the only info it gives is about the network adapter -- make sense to me.

</$0.02>

The way forward always starts with a minimal test.

Comment on Re: Win32 Network Adapter module naming Select or Download Code

Replies are listed 'Best First'.
Re^2: Win32 Network Adapter module naming by VinsWorldcom (Prior) on Sep 22, 2017 at 15:25 UTC
Thanks! Nit-picking, but technically twice :-P `use Win32::Really::Long::Module::Name::To::Get::Interface::Adapter::In +fo; ... my $if = Win32::Really::Long::Module::Name::To::Get::Interface::Adapte +r::Info->new();` [download] ... but point taken :-). Could always alias it as well. Three "levels" may be best - Win32::Net/Network::Interface/Adapter(::Info) - maybe optional fourth level of 'Info' in case someone wants to Win32::Net/Network::Interface/Adapter::Setter?	[reply] [d/l]

Replies are listed 'Best First'.

Re^2: Win32 Network Adapter module naming
by VinsWorldcom (Prior) on Sep 22, 2017 at 15:25 UTC

Thanks!

Nit-picking, but technically twice :-P

use Win32::Really::Long::Module::Name::To::Get::Interface::Adapter::In
+fo;
...
my $if = Win32::Really::Long::Module::Name::To::Get::Interface::Adapte
+r::Info->new();
[download]

... but point taken :-). Could always alias it as well. Three "levels" may be best - Win32::Net/Network::Interface/Adapter(::Info) - maybe optional fourth level of 'Info' in case someone wants to Win32::Net/Network::Interface/Adapter::Setter?

[reply]
[d/l]