Interesting, thanks! Didnt know about ANY before, and will sure find a use-case for it. Im not sure it will help me here though, it seems to me that an ANY will not accept a string assignment? I actually think that the "ALIAS" should work, that was a hard found error. I had a fair bit of scratching my head looking for misdirected pointers before I understood what was (not) happening. I will use the work-around of individual structs instead.
Apparently my construction will not work as any of the sub-types are not be able to accept any (further) value-initiation. Ie: string_item : log_data_base := (string_value := 'test', val_type := STRING_); is not eq to (the string_value will not be assigned): string_item_2 : log_data_string := (string_value := 'test'); Because effectively for the compiler this is eq. to a "double" assignment where the compiler sees only the first assignment (my guess). string_item_2 : log_data_base := (val_type :=...
Apparently my construction will not work as any of the sub-types are not be able to accept any (further) value-initiation. Ie: string_item : log_data_base := (string_value := 'test', val_type := STRING_); is not eq to (the string_value will not be assigned): string_item_2 : log_data_string := (string_value := 'test'); Because effectively for the compiler this is eq. to a "double" assignment where the compiler sees only the first assignment (my guess). string_item_2 : log_data_base := (val_type :=...
Apparently my construction will not work as any of the sub-types are not be able to accept any (further) value-initiation. Ie: string_item : log_data_base := (string_value := 'test', val_type := STRING_); is not eq to (the string_value will not be assigned): string_item_2 : log_data_string := (string_value := 'test'); Because effectively for the compiler this is eq. to a "double" assignment where the compiler sees only the first assignment (my guess). string_item_2 : log_data_base := (val_type :=...
Apparently my construction will not work as any of the sub-types are not be able to accept any value-initiation. Ie: string_item : log_data_base := (string_value := 'test', val_type := STRING_); is not eq to (the string_value will not be assigned): string_item_2 : log_data_string := (string_value := 'test'); Because effectively for the compiler this is eq. to a "double" assignment where the compiler sees only the first assignment (my guess). string_item_2 : log_data_base := (val_type := STRING_)...
A good start seems to be this YT from Jakob Sagatowski: https://www.youtube.com/watch?v=Vqk5Td-uWqk
Started playing with the idea of ditching windows for linux, one of the obstacles would be Codesys development. Alternatives: - linux with wine? - Run windows/codesys through virtual machine I guess a vm is the way to go? Anyone out there that could share their experience?
Easier that I thought, by ALIAS TYPE log_item_val_type : ( BOOL_ := 0, INT_, REAL_, STRING_ ); END_TYPE TYPE LOG_DATA_BASE STRUCT val_type : log_item_val_type; (* value, name etc *) ENDSTRUCT ENDTYPE TYPE LOG_DATA_BOOL : LOG_DATA_BASE := (val_type := log_item_val_type.BOOL_); END_TYPE TYPE LOG_DATA_INT : LOG_DATA_BASE := (val_type := log_item_val_type.INT_); END_TYPE TYPE LOG_DATA_REAL : LOG_DATA_BASE := (val_type := log_item_val_type.REAL_); END_TYPE TYPE LOG_DATA_STRING : LOG_DATA_BASE := (val_type...