in reply to (tye)Re: Symbol::List
in thread Devel::GetSymbols (fka Symbol::List)

Two saints say the Devel:: namespace is the place for this module to be, so I guess I'll have to change that then :)
How do you feel about the name Devel::Symbols? It's clear, short - and the plural indicates what it does. I'd like to avoid "list", if I'm going to put this outside of Symbol::, and I don't think Devel::Symbol::List would be such a great idea.

Let me know - reply and tell me what you think. 

2;0 juerd@ouranos:~$ perl -e'undef christmas'
Segmentation fault
2;139 juerd@ouranos:~$

[download]

Replies are listed 'Best First'.
Re: Re: (tye)Re: Symbol::List
by demerphq (Chancellor) on Jan 24, 2002 at 14:52 UTC
    Hmm. Well. Im a bit dense sometimes but I dont think I would immediately know what the package was for from Devel::Symbols, maybe Devel::PackgeSymbols?

    Just a thought.

    Yves / DeMerphq
    --
    When to use Prototypes?

[reply]
      I think PackageSymbols is too verbose, as only packages CAN have symbols :).
      It's like having the word "Object" in your object names, or naming every array "@array_foo" (with different foos).

      That's also why i would like to avoid "List" when not using Symbol::. What else would it supply? The name "Symbols" is plural, so you know it'll return multiple things - a list. (Any sane monk would be able to guess it won't return an arrayref :)

      Anyone else pro- or anti-Devel::Symbols? 

      2;0 juerd@ouranos:~$ perl -e'undef christmas'
Segmentation fault
2;139 juerd@ouranos:~$

      [download]

[reply]
[d/l]
Re: Re: (tye)Re: Symbol::List
by larryk (Friar) on Jan 24, 2002 at 16:28 UTC
    I don't see anything wrong with Devel::Symbol::List - it's not like it does anything more than this name suggests. To me Devel::Symbols sounds like a big module. If you don't want the extra level of ::, how about Devel::SymbolList? 
       larryk                                          
perl -le "s,,reverse killer,e,y,rifle,lycra,,print"
[reply]
      It's not about the level (the extra ::). I could really not care less, as I'm still working on Telephony::Siemens::X35 (which probably will never be finished).
      It's the use of "List". To me, the word "symbols" already implies a list, because it is plural. Module size and module name have nothing to do with each other. - 

      2;0 juerd@ouranos:~$ perl -e'undef christmas'
Segmentation fault
2;139 juerd@ouranos:~$

      [download]

[reply]
[d/l]

        A module called Devel::Symbols would seem to be a general-purpose symbol-handling utility. It should allow you to list symbols, delete symbols, dump symbols, etc. If you don't like "List", how about Devel::GetSymbols?

                - tye (but my friends call me "Tye")
[reply]
        What I meant was what tye (as he always does) managed to put into better words - Devel::Symbols says to me, "What do you want to do with Symbols today?" By big module I mean that the name infers that it would provide many functions for access/manipulation of the aforementioned "Symbols". Since your module only provides part of the functionality that I would hope a module named Devel::Symbols would I suggest that to name it so would be misleading. 
           larryk                                          
perl -le "s,,reverse killer,e,y,rifle,lycra,,print"
[reply]

In Section Meditations