[lvm-devel] [PATCH 4/4] Update tests for lvseg apis.

[Petr Rockai]

Zdenek Kabelac <zkabelac at redhat.com> writes:
>>> And I think using pointer would be wise decision here.
>> Care to elaborate? What's wise about using a pointer here?
>
> (const struct lvm_proper_value *v)
>
> avoid doing local copy of the 'v' structure - currently it's not a big
> difference, but as you pointed out in other emails - it could be extended in
> future. And I think we are using  pointers in other calls as well - so we
> should stay consistent also internally - and just pass pointers all the time -
> instead of thinking when to use struct and when the pointer should be passed.

Unlike object lifetime, this is something that the compiler can check
statically. Moreover, it may or may not be more efficient to pass a
pointer. Usually it's not, unless the structure is big and/or the
compiler optimisations poor.

Passing a value is prone to fewer errors. I vote for a value. (We should
aim to pass values whenever possible, IMHO. Those vg_t/pv_t/lv_t behave
as values as well, in this respect.)

Yours,
   Petr.