[gbd-dev] regexptest.php not up to date?

[Iassen H. <ih...@da...>]

It looks like the content of Gubed/ServerScripts/develop/ is not up to
date, because I do not get an explanation (and a link) on which line is the
error.

All I get is:

C:/apache2triad/htdocs/owl/phplib/test_mssql.php 55 lines Original file did
not parse

I am attaching the source of the full output HTML and the test_mssql.php
file that has the problem. I am sure it does have some syntax error in it,
so I am sure it is not an issue of parsing, but simply it does not display
what the error is.

I guess one peculiar thing is, I am running under MS Windows. PHP is 5.0.4,
not that it should matter.

--On Wednesday, July 06, 2005 06:09 +0200 Linus McCabe <Li...@mc...>
wrote:

> 
> Hi!
> 
> It was a while ago since a parsing error was reported... 
> Replace your GubedParserTokenizer.php file with the attached one and it
> should  work better.
> 
> About regexptest:
> I took the file you sent me and put it on my computer, in the dir 
> "Gubed/ServerScripts/develop" to be precise, but it can be anywhere.
> 
> Then I enter ./ in 'specify path' on the regexptest page. (ie, the path
> where  i put the file)
> 
> Then when i click "search" i get:
> 
> ...
> 1: ./testcode.php 3837 lines T_ARRAY: 'array' 
>    ***   Did not parse ok!   ***
> 2: ./regexptestcode.php 375 lines Parsed ok!
> 3: ./diffdisplay.php 123 lines Parsed ok!
> 4: ./index.php 26 lines Parsed ok!
> 5: ./postprocessdiff.php 68 lines Parsed ok!
> 6: ./regexptest.php 239 lines Parsed ok!
> 7: ./postprocess.php 21 lines Parsed ok!
> 8: ./regexptestcode_handmade.php 381 lines Original file did not parse
> ...
> 
> Ie, it tells me it could parse all files except the one you gave me
> (which i  saved as testcode.php when i saved it from the browser)
> 
> I can then click on 'Did not parse ok' which is a link.
> 
> Gubed will now show the code in modified (parsed) and unmodified versions
> side  by side as well as tell you what line it fails on. Sometimes the
> line is not  exact, since a parse error from gubed can result in a syntax
> error further  down (just like php give you the wrong line number
> sometimes).
> 
> I find the line it tells me and compare the parsed code to the original
> and  figure out what went wrong, this time it was very easy...
> 
> Anyway, you can always send unparsable files if you dont want to do this
> work  yourself.
> You're also encouraged to do the "Start scanning entire system
> (*nix/Linux  only)" on regexptest.php if you can and see if you have
> other unparsable  files...
> 
> Thanks for reporting the bug and let me know if it works better now!
> 
> cheers
> /Linus