in reply to Code Structures

two things:

I read an essay about Eclipse (the java IDE) that described Eclipse as moving toward more explicit representation of the deep structure ("code structure") of a program.

Internally it does represent these things to itself, which is how it knows how to refactor code in the various ways it does. In other words, it could be said to be parsing the source at a deeper level than just the surface syntax.

There might be something in the Eclipse community that resonates with what you are describing.

Replies are listed 'Best First'.
Re^2: Code Structures
by mugwumpjism (Hermit) on May 24, 2005 at 00:50 UTC

    You can already do something of the sort with PPI, but the problem is that the conventions for classes and many other "simple" things in Perl 5 make it less useful than with 'rigid' languages like Haskell, Java, etc.

    autrijus is one notable happy user of eclipse, when he's not using vim.

    This level of introspection, making it "easy" to edit Perl with refactoring editors is one of the goals of Perl 6. 

    $h=$ENV{HOME};my@q=split/\n\n/,`cat $h/.quotes`;$s="$h/."
."signature";$t=`cat $s`;print$t,"\n",$q[rand($#q)],"\n";

    [download]
[reply]
[d/l]

In Section Meditations