I got that - there is an issue with a potentially confusing (wrong) locations being shown depending on which mechanism is used to obtain the location. (It may report something that is not at all what you expect because it pickd up information about the location that is currently being lexed/parsed, while a problem may be triggered by evaluation of logic that was parsed earlier.  

The DevError is typically raised when there is an internal error and where there is no clear file/line association. (Then naturally :-/ the puppet error classes are used somewhat inconsistently, internal errors are sometimes caught and turned into ParseErrors (at points where location is actually known)).

This makes me reluctant to change the DevError without a more extensive search/check what the reported location will actually be in various scenarios.