(no subject)
Dec. 12th, 2001 02:27 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
cellioAha. It *is*, theoretically, a simple matter of programming.
A while ago, I described an API-validation problem. One of the tools I have available is the generated Javadoc for the candidate API. And Javadoc, as it turns out, does something reasonable if a method signature references a package it can't find: it simply spells out the name of the package, rather than providing its usual link. So, for example, if Foo is in the API and Bar is not, you'd get something like this:
where the underlining is really a link to the Javadoc for Foo.
Ok, fine and dandy; I have the beginnings of a grep-based solution. I can grep all the Javadoc looking for "com.mayaviz" -- but it's not that simple, because the legitimate links (like Foo) will have that in their URLs. So I can either post-process the grep output to throw out links, or avoid generating that output in the first place.
So what I *really* need is a very specialized parser: eat stuff until you find a <pre>, then until </pre> do this: eat everything in an <a>...</a>, and other than that if you find "com.mayaviz" spit out a report. Iterate until done.
Now I need to learn enough Perl to actually write the sucker... (I am not a Perl hacker. Not by a long shot.)
A while ago, I described an API-validation problem. One of the tools I have available is the generated Javadoc for the candidate API. And Javadoc, as it turns out, does something reasonable if a method signature references a package it can't find: it simply spells out the name of the package, rather than providing its usual link. So, for example, if Foo is in the API and Bar is not, you'd get something like this:
public void doSomething(Foo, com.mayaviz.something.Bar)
where the underlining is really a link to the Javadoc for Foo.
Ok, fine and dandy; I have the beginnings of a grep-based solution. I can grep all the Javadoc looking for "com.mayaviz" -- but it's not that simple, because the legitimate links (like Foo) will have that in their URLs. So I can either post-process the grep output to throw out links, or avoid generating that output in the first place.
So what I *really* need is a very specialized parser: eat stuff until you find a <pre>, then until </pre> do this: eat everything in an <a>...</a>, and other than that if you find "com.mayaviz" spit out a report. Iterate until done.
Now I need to learn enough Perl to actually write the sucker... (I am not a Perl hacker. Not by a long shot.)
Hm...
Date: 2001-12-13 02:33 am (UTC)search:
<.*>(.*)</.*>replace:
\1If I've done this correctly (it is 5:30am), it would strip out all html tags. No, wait, this won't handle nested tags. OK, a bit less brute forceish:
search:
<a.*>(.*)</a.*>- which would strip out your links. Then you can do your grep on the modified files. BBEdit lets you save searches, so you don't have to remember what exactly you got working every time the APIs change...I'm sure you could write something in perl to do what you want, but if you're not a perl hacker, the above might be faster. I'm having delusions that at one point I could've done what you wanted with just a combination of awk and grep, but like I said it is 5:30am...
Re: Hm...
From:Re: Hm...
From: