Re: C port of URI::* PLUS perl prog analyser?

PVHP@lns62.lns.cornell.edu
Mon, 10 Jun 1996 00:05:10 -0400 (EDT)


"Martin RJ Cleaver" writes on 9-JUN-1996 23:11:58.60:

!m.koster@webcrawler.com said:
!>Anyone know if a proper C implementation of URL's has been done?
!>(Yes, I know about libwww :()
!>A port of the Perl URI::* stuff would be great :-)
!
!I was figuring that a Java port would be interesting, at least
!from the architectural viewpoint.

With no regexps you might want to not hold your breath on that one.

!Which brings me to 2 another issues:
!  1) Is there/can there be a design document for LWP?
!		i.e. something showing what design decisions were made,
!		the inheritence employed etc.

dunno.

!  2) Anyone know of a tool to cross-reference Perl programs?
!		ie. to show module couplimg, what gets used from where etc?
!		- a braindead implementation is easy - you just grep for
!		names of subroutines. A more reliable implementation is
!		more tricky and would involve building a perl parser.

tkpod does a fantastic job of hyper-interlinking pod documents - provided that 
the pod author has taken the care to use L<> pod tags.

Assuming you use mwm, here is a Menu that you can add to your .mwmrc file 
(or .mwmrc.m4 for the X11R6.1 equipped :) to add tkpod (and friends) to your 
desktop GUI shell:

#----------------------8<--------------------------
Menu Perl
{
	"Perl"		f.title
        "editor"	f.exec "toy_edit &"
        "manual"	f.exec "tkpod perl.pod &"  # <- here ya go!!
        "the web"	f.exec "tkweb http://www.perl.com/perl/ &"
        "news"		f.exec "ptknews comp.lang.perl.misc &"
}
#---------------------->8--------------------------

Once you have that set up (I bind the menu to <MB-2>) then navigating through 
the entire perl manual with tkpod is a matter of clicking on the hyperlinks 
within the pod (actually you could have just said "tkpod perl.pod" right on the 
command line :-). It is literally faster than any web browser since at worst 
it uses NFS net communication protocols.

!		Of course, if we are going to have a perl parser it is 
!		better to be able to tap into the one already built into
!		Perl... would the structure of the innards of current perls
!		allow us to do this? Is there a perl module that does parsing
!		(none lept out at me when I looked)

There are plenty in development - Steve Lidie's Trace.pm kinda does what you 
want (I think :). There are others (with which I am not familiar).

Peter Prymmer
pvhp@lns62.lns.cornell.edu