Journal Efficiency

[DHuskic]

Journal Efficiency:
Could anyone help shed some light as far as best language to use with the journal in terms of efficiency and other important aspects to consider when choosing the best one? For example, between Eng-Tips and Gtac a majority of files I find for reference when starting a project are in .NET. Gtac holds more files of the other languages but is there a primary reason for most of them to be in .NET? Then also from the efficiency standpoint, each language has its pros and cons when programming but when compiled through NX, which works best? If anyone has any input they could share or personal preference as far as this, it would help immensely to hear your insight on this.

Denis Huskic
Data Prep NX7.5
Kettering University
Class of '17

 

[cowski]

If you are looking to run your code on different operating systems (windows, unix, linux, mac, etc), you should take a look at java. I know very little of java except that it has the reputation of producing the most 'portable' code.

The NXOpen API was (probably still is) based on C/C++; I've heard on Siemens' NXLanguages forum that there are a few API calls that depend on a data structure that has no direct translation to .net. Should you run across one of these functions that you need to use, it seems your only choice will be C/C++.

.Net provides memory management and a host of classes in the framework ready for use. Before .net, the main criticism of VB was slow execution speed. All of the .net languages get compiled to nearly identical bytecode; so speed of execution is nearly identical among the .net languages and are now on par with C++ code. You might be able to squeeze a little more performance out of C++ code, but it will come at a cost of more development time.

You should also post this question in the Siemens NXLanguages forum, you will most likely get more answers/opinions there.

www.nxjournaling.com