Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl-Sensitive Sunglasses
 
PerlMonks  

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

What is really needed is a perl parser (preferably in perl). There are the B:: modules, but they don't quite do what I want. I started tackling one a while back, but got distracted quite quickly. Idealy I want something that takes perl and cuts it into a parse tree at least at the sub (method) level, preserving all whitespace (at least within subs).

You're right though, there is no reason really to make it into a more binary-like scheme, except for maybe load-time (which considering all the interpreting going on doesn't seem like a problem at this point, and could easily be changed later).

As for an actual pragmatic use of this thing, I would definately need a clean way of allowing CPAN and other modules / scripts to be integrated into the environment. I would either have to (at least partially) give up the full-OO feel, or just use them as external references. Now that I'm thinking about it, using them as external references is a much better idea (though some of the OO could still be given up I suppose).

My mind swims with all the thoughts and ideas involved in creating a wonderful programming environment around the basic concept of making it smalltalk-like :)

Damn I love Perl.


In reply to Re: Re: Smalltalk-like browser for perl by awwaiid
in thread Smalltalk-like browser for perl by awwaiid

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others taking refuge in the Monastery: (3)
As of 2021-06-13 21:56 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    What does the "s" stand for in "perls"? (Whence perls)












    Results (58 votes). Check out past polls.

    Notices?