Search the Community
Showing results for tags 'operation'.
-
Here is a question I am pondering: The UML specification defines ParameterDirectionKind (7.3.43 in the V2.4.1 superstructure specification, available at omg.org) for an operation defined on a class. The description there is: "ParameterDirectionKind is an enumeration of the following literal values: • in Indicates that parameter values are passed into the behavioral element by the caller. • inout Indicates that parameter values are passed into a behavioral element by the caller and then back out to the caller from the behavioral element. • out Indicates that parameter values are passed from a behavioral element out to the caller. • return Indicates that parameter values are passed as return values from a behavioral element back to the caller." So, do we model the outputs of a LabVIEW class method (VI) with the "out" or "return" direction? I decided long ago to use "out" and never "return" for a number of reasons (some theoretical, some practical: "inout" does make sense, after all; many languages support only one return value, although this is a design choice), and I delete "void" for the return type in the operation prototype since I regard that as meaningless for LabVIEW. I still think that is the best approach, but I'm not certain that I have the most rigorous explanation, and of course I could be wrong altogether. Thoughts? Paul
-
Hi..my name is Sarat Paluri..did anyone work on doing remote access of experiments.I am presently working on the stress analysis of a cantilever beam.Can anyone please help me if they have worked before on this.