NetNews Usenet Archive 1992 #19/NN_1992_19.iso/spool/comp/lang/perl/5658

Text File | 1992-09-01 | 1.8 KB | 34 lines

Newsgroups: comp.lang.perl
Path: sparky!uunet!zaphod.mps.ohio-state.edu!malgudi.oar.net!caen!destroyer!ncar!csn!cherokee!lookout.it.uswc.uswest.com!rray
From: [e-mail] (Randy J. Ray)
Subject: Yet Another Silly Question (YASQ?)
Message-ID: <[e-mail]>
Sender: rray@snakepit (Randy J. Ray)
Nntp-Posting-Host: snakepit.it.uswc.uswest.com
Organization: US WEST Communications, Inc. -- Denver, CO
Date: Tue, 1 Sep 1992 17:17:42 GMT
Lines: 22

I have heard it said that nothing can parse perl except perl. Well, I am having
trouble even with that approach!

I am tasked with writing a small (at least, it started small) script to check
the validity of subroutine calls, specifically checking argument number and
type to the actually declaration. At this stage, I am still determining what
rules, or more specifically, execeptions to use in the actual test. That is not
the problem. Neither is extracting the subroutine definitions. That part is
done. I am having trouble parsing out the subroutine calls themselves. I need
to be able to extract the call, and it's list of parameters. Because of the
possibility of passing the result of a subroutine call, it might be a recursive
solution. Then there's the problem of passing the results of operations, like
"keys" or "sort" or others. Has anyone done anything like this? I looked
through the perldb.pl code, hoping to find some parsing clues, but to no avail.

Randy
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Randy J. Ray -- U S WEST IT/CSD         rray@{lookout,uswat}.it.uswc.uswest.com
I'd rather talk religion with Charles Manson than discuss ethics with Congress.
     -me                                                   Phone: [phone]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~