4.3 Common Errors Made While Interpreting A Source File

If there are compilation errors when you interpret a UDF source file, they will appear in the console. However, you may not see all the error messages if they scroll off the screen too quickly. For this reason, you may want to disable the Display Assembly Listing option while debugging your UDF. You can view the compilation history in the log file that is saved in your working folder.

If you keep the Interpreted UDFs dialog box open while you are in the process of debugging your UDF , the Interpret button can be used repeatedly since you can make changes with an editor in a separate window. Then, you can continue to debug and interpret until no errors are reported. Remember to save changes to the source code file in the editor window before trying to interpret again.

One of the more common errors made when interpreting source files is trying to interpret code that contains elements of C that the interpreter does not accommodate. For example, if you have code that contains a structured reference call (which is not supported by the C preprocessor), the interpretation will fail and you will get an error message similar to the following:

Error: /nfs/clblnx/home/clb/fluent/udfexample.c: 
line 15: structure reference