in reply to Re: When does programming become automatic (if ever)?
in thread When does programming become automatic (if ever)?

Talking about "automatisms" ...

> I still don't always remember the order of arguments to substr or splice,

that's actually a good idea for extending snippets in my IDE (yasnippet/Emacs) ¹

> what I can do is type perldoc -f splice at lighting speed

actually I could also expand the embedded documentation to reflect this in my IDE

> at lighting speed...

unfortunately not at light speed, often you are redirected to other perldocs

like in 

perldoc -f m

        m//     The match operator.  See perlop.

[download]

Cheers Rolf
(addicted to the Perl Programming Language and ☆☆☆☆ :)
Je suis Charlie!

¹) other suggestions for not memorable interfaces? caller ? what else ?

  • Comment on Re^2: When does programming become automatic (if ever)? (IDE support)
  • Download Code

Replies are listed 'Best First'.
Re^3: When does programming become automatic (if ever)? (IDE support)
by Anonymous Monk on Apr 13, 2016 at 09:19 UTC
    often you are redirected to other perldocs

    That was kind of the point: Knowing when to look in perlre, perlop etc. helps!

[reply]
[reply]
Re^3: When does programming become automatic (if ever)? (IDE snippets)
by LanX (Saint) on Apr 13, 2016 at 22:16 UTC
    > that's actually a good idea for extending snippets in my IDE (yasnippet/Emacs) ¹

    for the records some trivial templates for yasnippet, which is derived from textmates standard and is similar to snippMate for vim.

    Not too far away from Abbrevations in Komodo.

    # -*- mode: snippet -*-
# name: caller;
# key: caller
# --
my (${1:$package}, ${2:$filename}, ${3:$line}) = caller;
$0

    [download]

    # -*- mode: snippet -*-
# name: caller(LEVEL)
# key: caller
# --
my (${2:$package}, ${3:$filename}, ${4:$line}, ${5:$subroutine}, ${6:$
+hasargs},
${7:$wantarray}, ${8:$evaltext}, ${9:$is}_require, ${10:$hints}, ${11:
+$bitmask},
${12:$hinthash}) = caller(${1:$LEVEL});
$0

    [download]

    please note that both versions of caller are expanded with the same keyword + TAB and you can chose from a dropdown between both versions.

    here the example for splice

    # -*- mode: snippet -*-
# name: splice @ARR ,OFFSET ,LENGTH ,LIST
# key: splice
# --
splice @${1:ARR} ,${2:OFFSET} ,${3:LENGTH} , ${4:LIST...};

    [download]

    since I can include code (elisp but also bash or Perl) I'd like to find a way to delete the commas of skipped arguments instead of creating 4 versions for drop down... but I'm still at the beginning.

    Vision: Ideally these snippets could be generated from POD-examples and show the documentation¹, I think DBI is a good candidate.

    Cheers Rolf
    (addicted to the Perl Programming Language and ☆☆☆☆ :)
    Je suis Charlie!

    PS: thanks to Tux for suggesting the return values for stat, (local)time, and caller (with or without args)

    ¹) probably best realized in combination with autocomplete-mode ... unfortunately emacs-wiki seems to be down at the moment...

[reply]
[d/l]
[select]

In Section Meditations