Hey everyone! 👋 Today, we’re going to explore a handy function in the Uniface 10.4 low-code platform: $ude("load"). If you’ve ever needed to programmatically inspect the inner workings of your compiled Uniface objects, this function is your new best friend.

Quick note: This article was created with the help of an AI to break down the official documentation into a simple, easy-to-understand guide.

What is $ude(“load”)? 🤔

In simple terms, the $ude("load") function allows you to load the contents of a script listing or a symbol table from a compiled Uniface object directly into a variable or field in your application. Think of it as dynamically opening a “behind-the-scenes” file that Uniface creates during compilation.

This is incredibly useful for:

• Advanced Debugging: Creating your own custom logging or analysis tools.
• Dynamic Analysis: Building utilities to check dependencies or script contents at runtime.
• Auditing: Generating reports on what’s inside your compiled components without manually looking them up.

How to Use It: The Syntax Breakdown 🛠️

The syntax looks a bit complex at first, but it’s quite logical. Here it is:

$ude("load", "Type;ResourceType", ResourceName, {OptionList})

Let’s break down each part:

• "load": This is the fixed part of the function call that tells the Uniface Development Environment (UDE) what to do.

• Type: This tells the function what you want to load. You have two choices:

• symbolTable: Loads the symbol table.

• listing: Loads the ProcScript listing.

• ResourceType: This specifies the kind of Uniface object you’re targeting. Examples include component, service, form, or model.

• ResourceName: The actual name of your component or object (e.g., “MY_SERVICE”).

• OptionList: This is an optional list for more specific cases, like when dealing with global objects. Here you might need to specify a library or language.

A Practical Example in Action 💻

The best way to learn is by seeing it work. The code below first checks if a script listing for a component exists and, if it does, loads it into a variable and saves it to a text file.

variables
string vStatus, vListing, vName
endvariables

; Let's assume vName contains the name of our component, for example, "C_MY_COMPONENT"
vName = "C_MY_COMPONENT"

; First, check if the listing actually exists to avoid errors!
vStatus = $ude("Exist", "Listing;Component", vName, "", "")

if (vStatus = 0)
putmess "A listing for %%%vName does not exist 😔"
elseif (vStatus = 1)
; The listing exists, so let's load it!
vListing = $ude("Load", "Listing;Component", vName, "", "")

; Now we can do something with it, like dump it to a file
lfiledump/append vListing, "listing.txt"
putmess "Listing for %%%vName was successfully saved to listing.txt! ✨"
endif

Common Problems and Tips ⚠️

When using $ude("load"), keep these points in mind to avoid common issues:

1. Variable Size is Crucial: The content of a script listing can be very large! Make sure the variable or field you are loading the data into (like vListing in our example) is defined with a large enough size. If it’s too small, the data will be truncated.
2. Check Before You Load: As shown in the example, always use $ude("Exist", ...) before calling $ude("load"). This prevents your script from failing if the compiled resource or its listing doesn’t exist.
3. Global Objects Need More Info: If you are trying to load a listing from a global object (like a global Proc entry), you must provide the library name in the OptionList (e.g., "library=MY_LIBRARY").

Conclusion

And that’s it! The $ude("load") function is a powerful tool for developers who want to dig deeper into their Uniface applications at runtime. It’s perfect for building custom development and analysis tools right within the Uniface environment.

Happy coding! 😊