|
[Sponsors] |
what's the difference:interpreted and combiled udf |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
June 19, 2003, 05:03 |
what's the difference:interpreted and combiled udf
|
#1 |
Guest
Posts: n/a
|
About different methods to combile your udf, how can you select it? What is the difference between them?
Many thanks! |
|
June 19, 2003, 20:51 |
Re: what's the difference:interpreted and combiled
|
#2 |
Guest
Posts: n/a
|
Please read UDF manual6.1 Section 1.6 at Page 1-6
It helps. Rookie. |
|
June 20, 2003, 10:03 |
Re: what's the difference:interpreted and combiled
|
#3 |
Guest
Posts: n/a
|
Compiled UDF's are much better. They are more difficult to implement but it is worth investing the time to learn how to do them.
|
|
June 20, 2003, 13:18 |
Re: what's the difference:interpreted and combiled
|
#4 |
Guest
Posts: n/a
|
The most important differences are in capabilities and velocity of execution.
Using interpreted UDF, you can read and write data only using pre-defined macros. This kind of UDF is portable to all platform (Windows, Unix), but they're slower to execute. Compiled UDF are not portable (you have to recompile them if you change platform), but are faster and offer you complete access to data. A suggestion: Use UDF for easy tasks like implementing boundary conditions or profiles. Pass to compiled UDF if you have to implement more complex things like a complete model or a scalar equation. Hi ap |
|
|
|