You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PG problems stop processing when they hit the first ENDDOCUMENT(); call, and sometimes authors will put older code after this. If that code has errors, the problem will run fine but formatting the code with perltidy will error out.
This is a very minor issue, but should perltidy also ignore all code after the first ENDDOCUMENT(); call, since it isn't being used anyways? Also would this also be an issue with the convert to PGML option, should it also ignore any code after the first ENDDOCUMENT();?
The text was updated successfully, but these errors were encountered:
PG problems stop processing when they hit the first
ENDDOCUMENT();
call, and sometimes authors will put older code after this. If that code has errors, the problem will run fine but formatting the code with perltidy will error out.This is a very minor issue, but should perltidy also ignore all code after the first
ENDDOCUMENT();
call, since it isn't being used anyways? Also would this also be an issue with the convert to PGML option, should it also ignore any code after the firstENDDOCUMENT();
?The text was updated successfully, but these errors were encountered: