I'm a bit puzzled by the semantics of the .spec files: Given the 9 possible combinations of directions (in, out, in/out) and transfer types (value, reference, array), what do they mean exactly? E.g.
In C-speak, roughly func(BarPointer foo) func(const Bar *foo) func(const Bar foo[<whatever>]) The generator scripts and spec files evolved over many years (judging from the comments, early work was a
OK, perhaps the example was not really good, but I still can't grasp the intended differences between e.g. param foo BarPointer in value and param foo Bar out reference They *are* quite arbitrary in
There really isn't one from the standpoint of what the .spec files are used for today, though I wouldn't recommend using the prior form because it throws away some information and requires another ty
I'm a bit puzzled by the semantics of the .spec files: Given the 9 possible combinations of directions (in, out, in/out) and transfer types (value, reference, array), what do they mean exactly? E.g.
In C-speak, roughly func(BarPointer foo) func(const Bar *foo) func(const Bar foo[<whatever>]) The generator scripts and spec files evolved over many years (judging from the comments, early work was a
OK, perhaps the example was not really good, but I still can't grasp the intended differences between e.g. param foo BarPointer in value and param foo Bar out reference They *are* quite arbitrary in
There really isn't one from the standpoint of what the .spec files are used for today, though I wouldn't recommend using the prior form because it throws away some information and requires another ty