You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello Sir, i have a question asking for your help. Based on my understanding,we cannot ignore 'source_text' in subprogram, but i found in '/ocarina-build/ocarina/doc/source/ping/devices.aadl' at line21 where the special subprogram has no 'source_text'. It confused me.
thanks for your replay!
The text was updated successfully, but these errors were encountered:
What do you mean by "we cannot ignore source_text in source program"? A model is perfectly valid if subprograms do not define source_text. However it may not be correct for a specific model processing if absent. For instance, scheduling analysis does not need this property defined, but code generation does. Since code generation may not consider device, it is fine.
What do you mean by "we cannot ignore source_text in source program"? A model is perfectly valid if subprograms do not define source_text. However it may not be correct for a specific model processing if absent. For instance, scheduling analysis does not need this property defined, but code generation does. Since code generation may not consider device, it is fine.
I do not understand. If i do code generation work use software component without 'source_text' in subprogram, how can i confirm which file to execute when call a subprogram and where is the function 'subprogram_b'? Example like this:
SUBPROGRAM subprogram_b
features
subb_port: in parameter Base_Types::integer;
PROPERTIES
SOURCE_LANGUAGE => (C);
SOURCE_NAME => "subprogram_b";
END subprogram_b;
Hello Sir, i have a question asking for your help. Based on my understanding,we cannot ignore 'source_text' in subprogram, but i found in '/ocarina-build/ocarina/doc/source/ping/devices.aadl' at line21 where the special subprogram has no 'source_text'. It confused me.
thanks for your replay!
The text was updated successfully, but these errors were encountered: