![]() ![]() Hopefully that use is parallel to the use of compile time, compile-time, and compiletime. I don't think it even has to mandate that there be a run-time system.Īnyway: the issue here is that the spec should at least be self-consistent with respect to the use of run time, run-time, and runtime. The spec has no reason to mention the runtime. A runtime type is a type that is used in the implementation of the run-time system and it might not even be a Dart type at all. Likewise, a run-time type described by the spec is the type of a Dart object at run time. time to complete and show the output whereas the same query in our current production (Oracle 10G) environment is taking just a few seconds. A run-time error mandated by the spec represents the proper functioning of the runtime and is therefore not a runtime error. Particularly 3 SQL queries are taking almost 50 min. A runtime error is an error in the run-time system. ![]() For example, a run-time error is one that happens at run time. The adjective 'runtime' describes things that pertain to the runtime (in other words, the run-time system). The adjective 'run-time' describes things that pertain to run time. ![]() The spec absolutely should not use the adjective 'runtime' to describe this lifecycle phase for the same reason it should not use 'compiletime'. This parallels 'compile-time' which is the adjective form of 'compile time'. The adjective form of 'run time' (the program lifecycle phase in your linked Wikipedia page) is 'run-time'. Still, using it as a noun for the run-time system isn't really incorrect. It's ugly to read in my opinion and easily avoided anyway. The noun 'runtime' is jargon which comes from taking the adjective in the phrase 'run-time system' and turning it into a noun. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |