Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #207864 > unrolled thread

Net::DNS::Nameserver

Back to article view | Back to linux.debian.user

Contents

  Net::DNS::Nameserver mick crane <mick.crane@gmail.com> - 2019-04-26 13:20 +0200
    Re: Net::DNS::Nameserver Alberto Luaces <aluaces@udc.es> - 2019-04-26 13:40 +0200
      Re: Net::DNS::Nameserver mick crane <mick.crane@gmail.com> - 2019-04-26 13:50 +0200
    Re: Net::DNS::Nameserver <tomas@tuxteam.de> - 2019-04-26 13:50 +0200
      Re: Net::DNS::Nameserver mick crane <mick.crane@gmail.com> - 2019-04-26 14:20 +0200
        Re: Net::DNS::Nameserver Joe <joe@jretrading.com> - 2019-04-26 14:50 +0200
      Re: Net::DNS::Nameserver Cindy Sue Causey <butterflybytes@gmail.com> - 2019-04-26 22:30 +0200
        Re: Net::DNS::Nameserver mick crane <mick.crane@gmail.com> - 2019-04-27 00:20 +0200
          Re: Net::DNS::Nameserver Erik Christiansen <dvalin@internode.on.net> - 2019-04-27 04:10 +0200
            Re: Net::DNS::Nameserver <tomas@tuxteam.de> - 2019-04-27 09:00 +0200

#207864 — Net::DNS::Nameserver

sorry to be a nuisance
can somebody explain generally what this scheme of things with the dots 
has to do with ?
seen this in perl as the kind of hierarchy of modules but how is this to 
do with the OS ?

~$ apropos nameserver
Net::DNS::Nameserver (3pm) - DNS server class


mick

-- 
Key ID    4BFEBB31

[toc] | [next] | [standalone]

#207865

mick crane writes:

> sorry to be a nuisance
> can somebody explain generally what this scheme of things with the
> dots has to do with ?
> seen this in perl as the kind of hierarchy of modules but how is this
> to do with the OS ?
>
> ~$ apropos nameserver
> Net::DNS::Nameserver (3pm) - DNS server class

It usually translates to directory separators (/).  In your case, it
points to

/usr/share/perl5/Net/DNS/Nameserver.pm

-- 
Alberto

[toc] | [prev] | [next] | [standalone]

#207866

On 2019-04-26 12:29, Alberto Luaces wrote:
> mick crane writes:
> 
>> sorry to be a nuisance
>> can somebody explain generally what this scheme of things with the
>> dots has to do with ?
>> seen this in perl as the kind of hierarchy of modules but how is this
>> to do with the OS ?
>> 
>> ~$ apropos nameserver
>> Net::DNS::Nameserver (3pm) - DNS server class
> 
> It usually translates to directory separators (/).  In your case, it
> points to
> 
> /usr/share/perl5/Net/DNS/Nameserver.pm

Ah OK, I thought it might be some new scheme of things.

-- 
Key ID    4BFEBB31

[toc] | [prev] | [next] | [standalone]

#207867

[Multipart message — attachments visible in raw view] — view raw

On Fri, Apr 26, 2019 at 12:19:09PM +0100, mick crane wrote:
> sorry to be a nuisance

You are not (not to me, at least :-)

> can somebody explain generally what this scheme of things with the
> dots has to do with ?
> seen this in perl as the kind of hierarchy of modules but how is
> this to do with the OS ?
> 
> ~$ apropos nameserver
> Net::DNS::Nameserver (3pm) - DNS server class

You mean those double colons ('::')?

If yes: those are just separators for the Perl module namespace, which
conceptually is a hierarchy. At the (right) end you can put some object
(function, variable) living in that module's [1] namespace.

Those are just a device to subdivide the namespace and to organize
file system "places" [1] -- they have no intrinsic "meaning" to perl
(i.e. the language itself has no notion of "Net" or "Net::DNS" -- just
of "Net::DNS::Nameserver").

Cf "perldoc -f require" for the full thing :-)

Cheers

[1] In Perl parlance, it is a "package".
[2] Typically you'll find the package code in Net/DNS/Nameserver.pm
   under a suitable "module root", e.g. /usr/share/perl5. The whole
   list of roots is in the special array variable @INC.

-- tomás

[toc] | [prev] | [next] | [standalone]

#207869

On 2019-04-26 12:48, tomas@tuxteam.de wrote:
> On Fri, Apr 26, 2019 at 12:19:09PM +0100, mick crane wrote:
>> sorry to be a nuisance
> 
> You are not (not to me, at least :-)
> 
>> can somebody explain generally what this scheme of things with the
>> dots has to do with ?
>> seen this in perl as the kind of hierarchy of modules but how is
>> this to do with the OS ?
>> 
>> ~$ apropos nameserver
>> Net::DNS::Nameserver (3pm) - DNS server class
> 
> You mean those double colons ('::')?
> 
> If yes: those are just separators for the Perl module namespace, which
> conceptually is a hierarchy. At the (right) end you can put some object
> (function, variable) living in that module's [1] namespace.
> 
> Those are just a device to subdivide the namespace and to organize
> file system "places" [1] -- they have no intrinsic "meaning" to perl
> (i.e. the language itself has no notion of "Net" or "Net::DNS" -- just
> of "Net::DNS::Nameserver").
> 
> Cf "perldoc -f require" for the full thing :-)
> 
> Cheers
> 
> [1] In Perl parlance, it is a "package".
> [2] Typically you'll find the package code in Net/DNS/Nameserver.pm
>    under a suitable "module root", e.g. /usr/share/perl5. The whole
>    list of roots is in the special array variable @INC.
> 
> -- tom??s

thanks, I don't think I'll ever properly comprehend this stuff but I do 
like it when things work.

mick


-- 
Key ID    4BFEBB31

[toc] | [prev] | [next] | [standalone]

#207870

On Fri, 26 Apr 2019 13:09:46 +0100
mick crane <mick.crane@gmail.com> wrote:

> On 2019-04-26 12:48, tomas@tuxteam.de wrote:
> > On Fri, Apr 26, 2019 at 12:19:09PM +0100, mick crane wrote:  
> >> sorry to be a nuisance  
> > 
> > You are not (not to me, at least :-)
> >   
> >> can somebody explain generally what this scheme of things with the
> >> dots has to do with ?
> >> seen this in perl as the kind of hierarchy of modules but how is
> >> this to do with the OS ?
> >> 
> >> ~$ apropos nameserver
> >> Net::DNS::Nameserver (3pm) - DNS server class  
> > 
> > You mean those double colons ('::')?
> > 
> > If yes: those are just separators for the Perl module namespace,
> > which conceptually is a hierarchy. At the (right) end you can put
> > some object (function, variable) living in that module's [1]
> > namespace.
> > 
> > Those are just a device to subdivide the namespace and to organize
> > file system "places" [1] -- they have no intrinsic "meaning" to perl
> > (i.e. the language itself has no notion of "Net" or "Net::DNS" --
> > just of "Net::DNS::Nameserver").
> > 
> > Cf "perldoc -f require" for the full thing :-)
> > 
> > Cheers
> > 
> > [1] In Perl parlance, it is a "package".
> > [2] Typically you'll find the package code in Net/DNS/Nameserver.pm
> >    under a suitable "module root", e.g. /usr/share/perl5. The whole
> >    list of roots is in the special array variable @INC.
> > 
> > -- tom??s  
> 
> thanks, I don't think I'll ever properly comprehend this stuff but I
> do like it when things work.
> 
What you're probably more interested in is getting modules as Debian
packages where possible. Where they exist, they are normally called
something like libnet-dns-nameserver-perl (not a real Debian package,
by the way), adding 'lib' at the beginning, '-perl' at the end and
replacing the doubled colons with hyphens, all lower case. If that isn't
exactly right, a search should find what you want.

But there's a *lot* of perl... and only a subset is packaged in Debian.

-- 
Joe

[toc] | [prev] | [next] | [standalone]

#207886

On 4/26/19, tomas@tuxteam.de <tomas@tuxteam.de> wrote:
> On Fri, Apr 26, 2019 at 12:19:09PM +0100, mick crane wrote:
>
>> can somebody explain generally what this scheme of things with the
>> dots has to do with ?
>> seen this in perl as the kind of hierarchy of modules but how is
>> this to do with the OS ?
>>
>> ~$ apropos nameserver
>> Net::DNS::Nameserver (3pm) - DNS server class
>
> You mean those double colons ('::')?
>
> If yes: those are just separators for the Perl module namespace, which
> conceptually is a hierarchy. At the (right) end you can put some object
> (function, variable) living in that module's [1] namespace.
>
> Those are just a device to subdivide the namespace and to organize
> file system "places" [1] -- they have no intrinsic "meaning" to perl
> (i.e. the language itself has no notion of "Net" or "Net::DNS" -- just
> of "Net::DNS::Nameserver").
>
> Cf "perldoc -f require" for the full thing :-)
>
> [1] In Perl parlance, it is a "package".
> [2] Typically you'll find the package code in Net/DNS/Nameserver.pm
>    under a suitable "module root", e.g. /usr/share/perl5. The whole
>    list of roots is in the special array variable @INC.


I just happened to start noticing the same format being used within
"apt-cache show" query feedback, too. Took a second to find a good
example. This is for "openshot" (video editor):

Tag: implemented-in::python, interface::graphical, interface::x11,
 role::program, scope::application, use::editing, works-with::audio,
 works-with::video, x11::application

I THOUGHT I had searched "apt-cache" using those tags when I first
noticed them. It's not working that way now. It must have been that
the description's author had used the same categories as keywords in
their product description.

Am "feeling like" I've seen something where we could search by tags.
Sounds like a handy place for something like that to work.

Those tags would save at least a little bit on the false hits if you
were able to search for any packages with a developer expressed "use"
of "editing". Then you narrow that search to more specific usage needs
by seeking anything that "works with (consumes) audio (files)" which
is, in fact, something that has been a question on this list at some
point. Seems like that "interface" applied to that remembered thread
because the User was wanting something... command line. :D

That X11 tag, my memory's saying it feels like there was a question
where a User was seeking something that needed to specifically be
X11-friendly, too..

There's something to be said for the wide-open wing-it method, though.
Pick any keyword, and see what new find bubbles to the top. I searched
on "dragonfly" the other day while waiting for them to show back up
and start chasing water sprays out in the yard this Spring. :)

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with birdseed *

[toc] | [prev] | [next] | [standalone]

#207889

On 2019-04-26 21:25, Cindy Sue Causey wrote:
> On 4/26/19, tomas@tuxteam.de <tomas@tuxteam.de> wrote:
>> On Fri, Apr 26, 2019 at 12:19:09PM +0100, mick crane wrote:
>> 
>>> can somebody explain generally what this scheme of things with the
>>> dots has to do with ?
>>> seen this in perl as the kind of hierarchy of modules but how is
>>> this to do with the OS ?
>>> 
>>> ~$ apropos nameserver
>>> Net::DNS::Nameserver (3pm) - DNS server class
>> 
>> You mean those double colons ('::')?
>> 
>> If yes: those are just separators for the Perl module namespace, which
>> conceptually is a hierarchy. At the (right) end you can put some 
>> object
>> (function, variable) living in that module's [1] namespace.
>> 
>> Those are just a device to subdivide the namespace and to organize
>> file system "places" [1] -- they have no intrinsic "meaning" to perl
>> (i.e. the language itself has no notion of "Net" or "Net::DNS" -- just
>> of "Net::DNS::Nameserver").
>> 
>> Cf "perldoc -f require" for the full thing :-)
>> 
>> [1] In Perl parlance, it is a "package".
>> [2] Typically you'll find the package code in Net/DNS/Nameserver.pm
>>    under a suitable "module root", e.g. /usr/share/perl5. The whole
>>    list of roots is in the special array variable @INC.
> 
> 
> I just happened to start noticing the same format being used within
> "apt-cache show" query feedback, too. Took a second to find a good
> example. This is for "openshot" (video editor):
> 
> Tag: implemented-in::python, interface::graphical, interface::x11,
>  role::program, scope::application, use::editing, works-with::audio,
>  works-with::video, x11::application
> 
> I THOUGHT I had searched "apt-cache" using those tags when I first
> noticed them. It's not working that way now. It must have been that
> the description's author had used the same categories as keywords in
> their product description.
> 
> Am "feeling like" I've seen something where we could search by tags.
> Sounds like a handy place for something like that to work.
> 
> Those tags would save at least a little bit on the false hits if you
> were able to search for any packages with a developer expressed "use"
> of "editing". Then you narrow that search to more specific usage needs
> by seeking anything that "works with (consumes) audio (files)" which
> is, in fact, something that has been a question on this list at some
> point. Seems like that "interface" applied to that remembered thread
> because the User was wanting something... command line. :D
> 
> That X11 tag, my memory's saying it feels like there was a question
> where a User was seeking something that needed to specifically be
> X11-friendly, too..
> 
> There's something to be said for the wide-open wing-it method, though.
> Pick any keyword, and see what new find bubbles to the top. I searched
> on "dragonfly" the other day while waiting for them to show back up
> and start chasing water sprays out in the yard this Spring. :)
> 
> Cindy :)

I did wonder if was some scheme I was unaware of.
I noticed a couple of weeks ago somebody used these "::" between words 
to identify something.
Like in apt you have
/var/lib/apt/lists/security.debian.org_debian-security_dists_buster_updates_main_source_Sources
made me think that these dots was some way of identifying a thing so 
that everything is the same over the whole wide world .
Or something like that.

mick

-- 
Key ID    4BFEBB31

[toc] | [prev] | [next] | [standalone]

#207890

On 26.04.19 23:09, mick crane wrote:
> I did wonder if was some scheme I was unaware of.
> I noticed a couple of weeks ago somebody used these "::" between words to
> identify something.
> Like in apt you have
> /var/lib/apt/lists/security.debian.org_debian-security_dists_buster_updates_main_source_Sources
> made me think that these dots was some way of identifying a thing so that
> everything is the same over the whole wide world .
> Or something like that.

More the opposite. i.e. make the tail end of the long::name::thingy
identifiable in a _restricted_ scope. The :: nomenclature first appeared
(to my eyes) in C++ several decades ago. For perl to adopt an existing
convention is a step forward for the language.

Here's a brief exchange describing ::, the scope-resolution operator:

https://stackoverflow.com/questions/15649580/using-in-c

Erik

-- 
Arguing that Java is better than C++ is like arguing that grasshoppers taste
better than tree bark.                                   - Thant Tessman

[toc] | [prev] | [next] | [standalone]

#207895

[Multipart message — attachments visible in raw view] — view raw

On Sat, Apr 27, 2019 at 12:05:18PM +1000, Erik Christiansen wrote:
> On 26.04.19 23:09, mick crane wrote:
> > I did wonder if was some scheme I was unaware of.

[...]

> More the opposite. i.e. make the tail end of the long::name::thingy
> identifiable in a _restricted_ scope. The :: nomenclature first appeared
> (to my eyes) in C++ several decades ago. For perl to adopt an existing
> convention is a step forward for the language.

Many languages have adopted the double-colon as a scope resolution
operator (Tcl, Ruby, I think PHP too). Some languages don't need
it, because scope resolution is delegated to an already existing
mechanism (e.g. object member resolution -- e.g. Lua, Python, the
Lisps).

Cheers
-- tomás

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web