I’ve been building compiled apps for the last twenty years and have a fair sense of what does and doesn’t generate runtime errors. After all, 4D did not intentionally create such differences just to make our lives miserable. In the meantime, perhaps a list of such known differences might be a starting point. The way to check for compiled behaviour is to run compiled, which can be done at any time during development. It does not tell if the code contains any potential runtime issues. They just run a syntax check, which only checks if the application does not contain any fatal contradictions that prevents it from being compiled at all. That said, I have noticed that many developers do not use “ restart compiled” in development. My guess is that a strict mode must be aware of all such logical differences and throw a fake runtime error in interpreted mode. REAL, INTEGER, LONGINT.Ĭompiled: Numeric arrays can not be mixed the source must match the type of the target. Interpretive: Numeric arrays can be mixed the source is copied to the type of the target. The differences are consequential, resulting from the hard fact that compiled code works in a different mode of operation. Behavioral differences between interpreted and compiled mode
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |