Trapping errors from Proparse

I am doing some work adding Proparse to ABL2DB in order to expand its capabilities.  The old Proparse had no version 11.x syntax, but Mike Fechner and Marian Edu added some and now John Green has added a couple more bits.  The problem we are having is that our current error handling is providing some help, but is not diagnostic for all errors.  I will put our current catch routine at the end.

Sometimes we will get an error message from Proparse with a line number in the program being parsed and a token, e.g., TABLE-SCAN, which was not in Proparse prior to version 1117.  In that case, we know exactly what syntax is the problem and can look at the code to tie it down.  E.g., in one case the token was LIKE and the line number pointed to a parameter definition for a method so that we knew that the problem was using LIKE in a method parameter definition.

But, we are also getting two types of errors that are not providing this information.  These are either org.prorefactor.refactor.RefactorException or a java.lang.NullPointerException.  In the latter case, we sometimes get a call stack, but not always and the call stack is not really helping me to find the source of the error.   Is there any additional error handling we can put in that would be likely to help (other than modifying Proparse itself, which is not in my control).

My current top level catch blocks are:

		catch eobAppError as Progress.Lang.AppError:
			log-manager:write-message ( eobAppError:ReturnValue ).	
			delete object eobAppError.
		end catch.
	
		catch eobSysError as Progress.Lang.SysError :
			log-manager:write-message(substitute("Unexpected Exception: &1", eobSysError:getMessage(1)), "SysERROR").
			if eobSysError:NumMessages > 1
			then do inWhich = 2 to eobSysError:NumMessages:
				log-manager:write-message(substitute("Unexpected Exception (cont.): &1", eobSysError:getMessage(inWhich)), "SysERROR").
			end.
			do inWhich = 1 to num-entries(eobSysError:CallStack,"~n"):
				log-manager:write-message(entry(inWhich,eobSysError:CallStack,"~n"),"CALLSTACK").
			end.
			delete object eobSysError no-error.
		end catch.
		
    catch eobOtherError as Progress.Lang.Error :
      log-manager:write-message(substitute("Other error: &2", eobOtherError:getMessage(1))).  
      if eobOtherError:NumMessages > 1
      then do inWhich = 2 to eobOtherError:NumMessages:
        log-manager:write-message(substitute("Unexpected Exception (cont.): &1", eobOtherError:getMessage(inWhich)), "OtherERROR").
      end.
      do inWhich = 1 to num-entries(eobOtherError:CallStack,"~n"):
        log-manager:write-message(entry(inWhich,eobOtherError:CallStack,"~n"),"CALLSTACK").
      end.
      delete object eobOtherError no-error.
    end catch.

So, no point in adding other catch blocks other than to give a more user friendly message with no actual useful additional information?