Compilation, RPO and patch application
Distinguishes source file, compiled object and update package.
Overview
Saving a PRW to Git does not compile it into the RPO. In official TDS-VSCode, configure server, environment and includes; compile and inspect AdvPL Output. CH-only changes may require dependent-source recompilation. A patch packages objects for a compatible destination; generating it proves neither application nor execution. Identify environment and versions, preserve a recovery strategy and test the package before updating production. The example is a data-free diagnostic source that distinguishes compilation from observable execution. (TOTVS, 2026, ref. 1)
Commented example
#Include "Protheus.ch"
User Function Ed308()
// This message appears only if the function executes.
ConOut("Editorial diagnostic: execution started")
Return NilThe message is expected only after invoking U_Ed308 in the correct test environment; this page does not prove compilation or patch application. Under review: editorial example neither compiled nor run in Protheus. Check includes, release, RDD and context before testing.
- Keep credentials out of configuration examples. Record package objects and versions; verify the target and run functional checks after updating.
- Under review: editorial example neither compiled nor run in Protheus. Check includes, release, RDD and context before testing.
Comments
There are no approved comments yet.
Sign in with Google or Microsoft to comment.