Talk:Runtime (program lifecycle phase)

What about undetected errors?

The article says "a run-time error is detected after or during the execution of a program" but some languages does not specify what will happen in certain situations. E.g. accessing array elements out of bounds, division by zero, etc. If these are not runtime errors, what are they? 213.67.240.59 (talk) 10:19, 17 August 2017 (UTC)

In a language like C which does not support array bounds checking, it's a bug, possibly resulting in a segmentation fault or corrupted data or some other type of crash. In langauges that support array bounds checking, this would be a runtime error. The article does not (currently) completely enumerate all runtime errors, and this may not be possible in a general article, as those are very language specific. --ssd (talk) 01:36, 19 July 2018 (UTC)

Runtime and Runtime environment

Runtime environment redirects here. Per Talk:Runtime environment, Runtime environment was apparently once a separate article which was merged here. Quotes from a couple of articles:

• "Adobe Integrated Runtime ... is a cross-OS runtime environment ..."
• "Microsoft Silverlight ... is a runtime for browser-based Rich Internet Applications ..." - (IMHO, this use of "runtime" is confusing and should be changed.)

The meanings of the terms "runtime" and "runtime environment" are sufficiently different that these should have separate articles, especially given the current development of new "runtime environments". -- Writtenonsand (talk) 18:43, 1 January 2008 (UTC)

Hey I added something and I think it needs to be improved: "Runtime error" - Conmiro —Preceding unsigned comment added by Conmiro (talk • contribs) 01:06, 26 February 2008 (UTC)

Runtimes and runtime environments are two totally different things. Unfortunately, this article contains interdependent descriptions; similar to the way good is only described as a juxtaposition against evil. As a contingency of seperating this one article into two, both parts will need more complete descriptions. —Preceding unsigned comment added by 67.232.190.211 (talk) 20:33, 9 January 2009 (UTC)

Agree, needs split. Runtime is the dynamic behaviour of a program, as opposed to its static behaviour (what it looks like). A runtime environment is a completely diferent thing; it's an API to provide common services and control. The leak of "virtual machine" is the giveaway... so what does the virtual machine run on in runtime? Another virtual machine? Ad infinitum? SimonTrew (talk) 20:17, 7 April 2009 (UTC)

Requested move

The following discussion is an archived discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. No further edits should be made to this section.

The result of the move request was: not moved. Skomorokh 14:45, 12 May 2011 (UTC)

---

Run time (computing) → Execution timeExecution time – Relisted. Jenks24 (talk) 02:59, 1 May 2011 (UTC) Current title is still ambiguous with respect to Run-time system, which also falls under the domain of "computing". Cybercobra (talk) 23:15, 20 April 2011 (UTC)

• Oppose The title does what it says on the can. Chaosdruid (talk) 22:31, 29 April 2011 (UTC)
  • How is that relevant? The issue with the current title isn't its accuracy but rather its ambiguity. --Cybercobra (talk) 23:43, 29 April 2011 (UTC)
• Oppose I think that "run time" is the common name. If true, the way to address ambiguity would be a different disambiguator. ErikHaugen (talk | contribs) 23:56, 9 May 2011 (UTC)

The above discussion is preserved as an archive of a requested move. Please do not modify it. Subsequent comments should be made in a new section on this talk page. No further edits should be made to this section.

Merge into Execution (computing)

The idea of "run time" and "execution" are inextricably linked; the separation of the two to separate articles results in duplication on the one hand, and missing content on the other. Also note that this article lists no sources. François Robere (talk) 12:18, 7 March 2023 (UTC)

Agree, bearing in mind some may call into a distinction between what happens before the address of the entry point is loaded by the OS - which is "runtime" but not execution, to whit the program_to_be is "running" and not executing.

Similarly, when the OS receives the program termination event, the OS resources reclamation post-program may be still considered as part of the "runtime".

Having said that, full deference is given to the information in the article regarding definitions of runtime/execution, and if (agreed on) differences in interpretation of the definitions are included in the article, am committed to fully supporting the merger. Lmstearn (talk) 16:08, 9 March 2023 (UTC)

  Y Merge completed Klbrain (talk) 17:14, 19 November 2023 (UTC)