Eric Wilhelm writes:
> # from Smylers
> # on Saturday 03 December 2005 03:41 am:
>
> > That sounds tedious when written down like this, but basically it
> > just involves holding down Ctrl and pressing P and X a few times.
>
> Neat. My vim does it all at once if the syntax mode is perl :-)
Ah,
# from Smylers
# on Saturday 03 December 2005 03:41 am:
>That sounds tedious when written down like this, but basically it just
>involves holding down Ctrl and pressing P and X a few times.
Neat. My vim does it all at once if the syntax mode is perl :-)
>> That said, I would much rather see all
* Smylers <[EMAIL PROTECTED]> [2005-12-03 12:45]:
> I believe that Emacs has an equivalent feature
Yeah, that camp calls it hippie-expand – don’t ask.
> and I'm sure I've seen some kind of tooltip completion feature
> on a gui Windows editor.
That’s common.
Eclipse also offers “word completion,
Eric Wilhelm writes:
> use My::Really::Long::Module::Name;
> my $obj = My::Really::Long::Module::Name->new();
>
> ... is just _almost_ tedious enough to warrant copy/paste, but not
> quite.
A decent editor should provide some sort of completion facility on
previously typed terms, so that y
On Fri, Dec 02, 2005 at 07:32:04PM -0800, Eric Wilhelm wrote:
> >It's better than the other examples, which doesn't mean it is good.
> > How about FileFormat:: ?
> >
> >FileFormat::GBF - Front end to GBF read/write interface
> >FileFormat::GBF::Parser
> >...
>
> Ok, but it's just SoooLoonng.
>
>
* Eric Wilhelm <[EMAIL PROTECTED]> [2005-12-03 11:05]:
> I tend to detest the long names that too much discussion about
> hierarchy has forced on us...
>
> use My::Really::Long::Module::Name;
> my $obj = My::Really::Long::Module::Name->new();
>
> ... is just _almost_ tedious enough to warrant c
# from Daniel T. Staal
# on Friday 02 December 2005 12:59 pm:
>It's better than the other examples, which doesn't mean it is good.
> How about FileFormat:: ?
>
>FileFormat::GBF - Front end to GBF read/write interface
>FileFormat::GBF::Parser
>...
Ok, but it's just SoooLoonng.
I think Austin has
Sorry, that should have been
$ perl -MModuleNumber::22 -le 'print 1'
Can't locate ModuleNumber/22.pm in @INC
> I think the interpreter might complain about that a bit-
>
> use 22;
>
> Perl v22.0.0 required (did you mean v22.000?)--this is only v5.8.6, stopped
> at -e line 1.
>
> :-)
>
> Austin
# perl -MModuleNumber22 -le 'print 1'
Can't locate ModuleNumber22.pm in @INC (@INC cont
On Fri, Dec 02, 2005 at 03:31:48PM -0600, David Nicol wrote:
> On 12/2/05, Austin Schutz <[EMAIL PROTECTED]> wrote:
>
> > As long as the name isn't taken and it has some amount of logic, I
> > doubt the name of a module makes any practical difference any more. It seems
> > like the days of
On 12/2/05, Austin Schutz <[EMAIL PROTECTED]> wrote:
> As long as the name isn't taken and it has some amount of logic, I
> doubt the name of a module makes any practical difference any more. It seems
> like the days of poring over proper module names should come to an end.
>
> *sh
On Fri, Dec 02, 2005 at 09:50:19AM -0800, Eric Wilhelm wrote:
> # from David Landgren
> # on Friday 02 December 2005 08:25 am:
>
> >In about 10 days time, I'm going to forget utterly that FF means File
> >Formats. Does it need to be so terse?
>
> Considering the number of file formats which curre
On Fri, December 2, 2005 12:50 pm, Eric Wilhelm said:
> Now consider the more comprehensible, discoverable single tree under
> FF::
>
> FF::GBF - Front end to GBF read/write interface
> FF::GBF::Parser
> FF::GBF::Bytes
> FF::GBF::DOM
> FF::GBF::Constants
> FF::GBF::Writer
> FF::GBF::Simple
> FF::G
# from David Landgren
# on Friday 02 December 2005 08:25 am:
>In about 10 days time, I'm going to forget utterly that FF means File
>Formats. Does it need to be so terse?
Considering the number of file formats which currently have toplevel
names, FF:: isn't that terse. Besides, search results s
14 matches
Mail list logo
