Beefy Boxes and Bandwidth Generously Provided by pair Networks
Just another Perl shrine
 
PerlMonks  

Re^5: Slow evolution of Perl = Perl is a closed Word (use)

by erroneousBollock (Curate)
on Sep 01, 2007 at 06:38 UTC ( [id://636489]=note: print w/replies, xml ) Need Help??


in reply to Re^4: Slow evolution of Perl = Perl is a closed Word (use)
in thread Slow evolution of Perl = Perl is a closed Word

W.r.t static analysis of perl, there would then seem to be a lot of things that would need to be sorted out (or at least heuristics provided for) to make it useful for the purposes of an IDE.

In fact, if someone is burdened1 by the use of syntax highlighting when editting their Perl code, then their coding style will be somewhat skewed such that they avoid even reasonable constructs if they happen to confuse their syntax highlighter.
Heh :-) I do use syntax-highlighting wherever possible, if only because it allows me (in my perception) to skim my code faster.

I mostly use Vim (I've been trying to use Emacs of late)... it has lots of problems with its very simplistic highlighter. I don't avoid the "problematic" constructs; I've just formed a habit of inserting comments to "correct" those mistakes ;)

My impression is that PPI, in practice, is good enough often enough that a PPI-based IDE could be successful if used on a new project (due to the feedback loop I noted above). The effectiveness of a PPI-based IDE when applied to an existing code base is certainly less certain, IMHO.
Well, it has to start somewhere (assuming that making perl "more available" to beginners/infidels is a worthwhile goal).

I agree that the feedback loop would eventually lead to a parser that works reasonably for arbitrary perl5 code.

-David.

Replies are listed 'Best First'.
Re^6: Slow evolution of Perl = Perl is a closed Word (use)
by ysth (Canon) on Sep 02, 2007 at 07:14 UTC
    I agree that the feedback loop would eventually lead to a parser that works reasonably for arbitrary perl5 code.
    I think you misunderstood. The feedback loop I see tye talking about is that programmers using syntax highlighting will tend to not use constructs the highlighter gets wrong, thus making the highlighting of the growing codebase closer and closer to perfect. That's the opposite of "arbitrary" perl5 code.

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://636489]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others exploiting the Monastery: (2)
As of 2024-03-19 06:11 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found