On Wednesday, July 31, 2002, at 06:43 , Scott Barnett wrote:
[..]
>  What is a good Perl Editor for writing scripts?

The Correct Answer is:

        The one on the machine where you do your editing.
        That simplifies the process for you.

I am partial to doing my development with bbedit 6.5.2
but also use 'vi' on machines where it is the only
installed 'fancy' editor.

Unfortunately these do not have some of the crucial
features that are required in a full Perl IDE - which
is what I believe you are really asking about.

Many editors now come with various forms of 'colour'
for providing 'syntax mark up' - that will provide
'visual clues' to when one has injected a 'typo' into
a script. This helps IF you know the 'colour schema'
for how perl syntax SHOULD look like to begin with. It
will of course help you along the way to learn basic
perl syntax as you use this 'memory aid'.

Amongst the features I find useful in the bbedit version
are such basic requirements as:

        a) the ability to call up the 'perl docs' for
                functions and modules -

                a1) select the thing you wonder about, and click
                        the view reference option.

                a2) when constructing POD in a script/code/module
                        one can also run the 'view POD' option to see
                        how the pod would lay out

        b) the ability to invoke the perl debugger

        c) the ability to run code in either a 'terminal' window
                or as a 'stand alone' ....

        d) Ability to Create and Utilize 'stationery' for code templates
                as well as 'glossaries' of 'hot-key' sequences for basic things
                one would normally have to type one's self.

Things that I have yet to find in any decent 'perl editor'
with ambitions to being a fully integraded development environment:

1. perl document searches that include all modules everywhere
        that will do a full search for the appropriate module one
        should have been using from the CPAN based upon some simple
        Regular Expression and/or Domain Specific Language Expansion
        style language that can resolve what the true intent would have been
        for the functionality one is seeking.

2. UML graphical presentation to Perl Code - such a suite would
        allow one to play with pictographs and various forms of hierogliphics
        to graphically represent the conceptual frame work that are then
        translated into an appropriate suite of Perl Modules and supporting
        scripts and code.

3. Apocalypse Now Redux - the directors cut, that will identify
        which portions of your current Perl5 coding style/habit/tendencies
        will become redundent and/or deprecated in Perl6, and no longer
        needed in Perl7.

4. The Correct Upgrader - this portion is the rational extension of
        the query mechanisms used in 1 above, based upon the resilience
        of section 3, as clarified by 2, that will

                4a) download and install while you type, the correct
                                CPAN modules - correcting and replacing any
                                deprecated code that you had previously typed

                4b) if no such module currently exists, will send out the
                                call for votes to form
                                        4b1 - the correct UseNet news group
                                        4b2 - the correct email group
                                        4b3 - the correct bridge between SMTP and NNTP
                                        4b4 - institutionalize such other alternative
                                                        messaging mechanisms as 
required.

                4c) Establish and Co-ordinate a working group both at the
                                CPAN, as well as within the IETF, to establish a
                                standards track for this solution space.

                4d) Interoperate with the dissident factions to create a
                                religious war over this solution space.

5. The Endless Coffee Pot - this portion of any reasonable Perl
        IDE will make sure that the 'stimulant based' fluid system is
        current with the requirements for neural enhancers.

6. Enhanced Management Interface Mechanisms - that will summarise
        all that one has done to date with regards to

                6a) open defects against the project
                6b) the timeline and budget of the project
                6c) shifts in the corporate policies with regards to
                                the allocation of stock options as they influence
                                the market position of the company and coder assets

                6d) as required, master meaningless marketting expressions
                        promulgated in the corporate email disinformation campaign
                        as well as responding to same in the lingua franca of the
                        current corporate psychoBabble

                6e) Organize and attend meetings with other Perl IDE systems
                                and/or Coders and/or Management Elements to establish
                                new and improved fruitless directions

7. X-EMIM - the extended version of EMIM - this includes the sub-system
        that provides the extensibility as required - including but not
        limited to

        7a) Creating New Technology Buzz
        7b) Identifiying Deprecated Technology Buzz
        7c) Establishing translation tables between the above and
                        the Marketting Speak interface modules.

8. Other features as required.

> I am currently using Crimson Editor.

looks neat, I may have to try it...


ciao
drieux

---

The Voices in my Head Make me do This....



-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to