Re: [RFC obexd 05/10] client-doc: replace parameter dict with conventional ones

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Luiz, Vinicius,

IMO it is better to leave as it is because then some parameters can be omitted such as adapter and target, and it also easier to extend if we need other parameters e.g. WHO header without breaking the signature.

This might be a matter of personal preference, but IMO using a dictionary to make an API more flexible is just hiding the problem. I don't see why this method has more reasons than any other method to use a dictionary instead of well-defined formal parameters.

If the point is that some of the input parameters are optional, I would rather propose using empty strings. Again, it's a matter of personal taste.

Besides, I don't understand how the target could be omitted. Could you further elaborate on this?

Cheers,
Mikel

--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux