I wrote a complex IDL as shown below:
struct Product { 1: string name, 2: string description }
After publishing this IDL, I noticed that the “description” is kind of “reserved” in iOS, because the class NSObjecthas a “description” class method , and this is IDLsupposed to be used in iOS.
NSObject
IDL
I thought about this topic and got some candidates:
But I could not understand which one is better (in terms of naturalness and conciseness), since I am not a native speaker of English.
, , , "" - iOS NSObject.
, description - NSObject.
description
, , , . ( ).
.
, "" - . - "" , , .
strName, strDescription .., , .
strName
strDescription
"" , (nameText, descriptionText) ..
nameText
descriptionText
: "", "" .. Apple .
, , . Apple , , .
struct, , C (struct C, Objective-C). , , .
struct
- . , Apple ( capitalizedString - capitalized, ? ). "descriptionProduct" "descriptionOfTheProduct" "descProduct". , , , "desc" , .
capitalizedString
capitalized
- REST, , , . , , "desc..." ( ).
, .
Since this is in struct, it does not conflict with the method named at all description. You can safely use it only descriptionhere.
However, perhaps you can also be more intelligent, descriptive in your name. What is a description that describes? The structure itself or the product that it represents? If the latter, productDescriptionwould be a great choice.
productDescription