Return to Answer

Objective-C methods are designed to be self documenting, and they borrow from the rich tradition of Smalltalk.

I'll try to explain what you have here, -(NSInteger) pickerView:(UIPickerView*)pickerView numberOfRowsInComponent:(NSInteger)component.

• - (NSInteger)
  This first portion indicates that this is an Objective C instance method that returns a NSInteger object. the - (dash) indicates that this is an instance method, where a + would indicate that this is a class method. The first value in parenthesis is the return type of the method.

• pickerView:
  This portion is a part of the message name. The full message name in this case is pickerView:numberOfRowsInComponent:. The Objective-C runtime takes this method information and sends it to the indicated receiver. In pure C, this would look like
  NSInteger pickerView(UIPickerView* pickerView, NSInteger component). However, since this is Objective-C, additional information is packed into the message name.

• (UIPickerView*)pickerView
  This portion is part of the input. The input here is of type UIPickerView* and has a local variable name of pickerView.

• numberOfRowsInComponent:
  This portion is the second part of the message name. As you can see here, message names are split up to help indicate what information you are passing to the receiver. Thus, if I were to message an object myObject with the variables foo and bar, I would type:
  [myObject pickerView:foo numberOfRowsInComponent:bar];
  as opposed to C++ style:
  myObject.pickerView(foo, bar);.

• (NSInteger)component
  This is the last portion of the input. the input here is of type NSInteger and has a local variable name of component.

Hopefully this is helpful!

Objective-C methods are designed to be self documenting, and they borrow from the rich tradition of Smalltalk.

I'll try to explain what you have here, -(NSInteger) pickerView:(UIPickerView*)pickerView numberOfRowsInComponent:(NSInteger)component.

• - (NSInteger)
  This first portion indicates that this is an Objective C instance method that returns a NSInteger object. the - (dash) indicates that this is an instance method, where a + would indicate that this is a class method. The first value in parenthesis is the return type of the method.

• pickerView:
  This portion is a part of the message name. The full message name in this case is pickerView:numberOfRowsInComponent:. The Objective-C runtime takes this method information and sends it to the indicated receiver. In pure C, this would look like
  NSInteger pickerView(UIPickerView* pickerView, NSInteger component). However, since this is Objective-C, additional information is packed into the message name.

• (UIPickerView*)pickerView
  This portion is part of the input. The input here is of type UIPickerView* and has a local variable name of pickerView.

• numberOfRowsInComponent:
  This portion is the second part of the message name. As you can see here, message names are split up to help indicate what information you are passing to the receiver. Thus, if I were to message an object myObject with the variables foo and bar, I would type:
  [myObject pickerView:foo numberOfRowsInComponent:bar];
  as opposed to C++ style:
  myObject.pickerView(foo, bar);.

• (NSInteger)component
  This is the last portion of the input. the input here is of type NSInteger and has a local variable name of component.

Objective-C methods are designed to be self documenting, and they borrow from the rich tradition of Smalltalk.

I'll try to explain what you have here, -(NSInteger) pickerView:(UIPickerView*)pickerView numberOfRowsInComponent:(NSInteger)component.

• - (NSInteger)
  This first portion indicates that this is an Objective C instance method that returns a NSInteger object. the - (dash) indicates that this is an instance method, where a + would indicate that this is a class method. The first value in parenthesis is the return value of the method.

• pickerView:
  This portion is a part of the message name. The full message name in this case is pickerView:numberOfRowsInComponent:. The Objective-C runtime takes this method information and sends it to the indicated receiver. In pure C, this would look like
  NSInteger pickerView(UIPickerView* pickerView, NSInteger component). However, since this is Objective-C, additional information is packed into the message name.

• (UIPickerView*)pickerView
  This portion is part of the input. The input here is of type UIPickerView* and has a local variable name of pickerView.

• numberOfRowsInComponent:
  This portion is the second part of the message name. As you can see here, message names are split up to help indicate what information you are passing to the receiver. Thus, if I were to message an object myObject with the variables foo and bar, I would type:
  [myObject pickerView:foo numberOfRowsInComponent:bar];
  as opposed to C++ style:
  myObject.pickerView(foo, bar);.

• (NSInteger)component
  This is the last portion of the input. the input here is of type NSInteger and has a local variable name of component.

Hopefully this is helpful!

Objective-C methods are designed to be self documenting, and they borrow from the rich tradition of Smalltalk.

I'll try to explain what you have here, -(NSInteger) pickerView:(UIPickerView*)pickerView numberOfRowsInComponent:(NSInteger)component.

• - (NSInteger)
  This first portion indicates that this is an Objective C instance method that returns a NSInteger object. the - (dash) indicates that this is an instance method, where a + would indicate that this is a class method. The first value in parenthesis is the return type of the method.

• pickerView:
  This portion is a part of the message name. The full message name in this case is pickerView:numberOfRowsInComponent:. The Objective-C runtime takes this method information and sends it to the indicated receiver. In pure C, this would look like
  NSInteger pickerView(UIPickerView* pickerView, NSInteger component). However, since this is Objective-C, additional information is packed into the message name.

• (UIPickerView*)pickerView
  This portion is part of the input. The input here is of type UIPickerView* and has a local variable name of pickerView.

• numberOfRowsInComponent:
  This portion is the second part of the message name. As you can see here, message names are split up to help indicate what information you are passing to the receiver. Thus, if I were to message an object myObject with the variables foo and bar, I would type:
  [myObject pickerView:foo numberOfRowsInComponent:bar];
  as opposed to C++ style:
  myObject.pickerView(foo, bar);.

• (NSInteger)component
  This is the last portion of the input. the input here is of type NSInteger and has a local variable name of component.

Hopefully this is helpful!

Objective-C methods are designed to be self documenting, and they borrow from the rich tradition of Smalltalk.

I'll try to explain what you have here, -(NSInteger) pickerView:(UIPickerView*)pickerView numberOfRowsInComponent:(NSInteger)component.

• - (NSInteger)
  This first portion indicates that this is an Objective C instance method that returns a NSInteger object. the - (dash) indicates that this is an instance method, where a + would indicate that this is a factory method. The first value in parenthesis is the return value of the method.

• pickerView:
  This portion is a part of the message name. The full message name in this case is pickerView:numberOfRowsInComponent:. The Objective-C runtime takes this method information and sends it to the indicated receiver. In pure C, this would look like
  NSInteger pickerView(UIPickerView* pickerView, NSInteger component). However, since this is Objective-C, additional information is packed into the message name.

• (UIPickerView*)pickerView
  This portion is part of the input. The input here is of type UIPickerView* and has a local variable name of pickerView.

• numberOfRowsInComponent:
  This portion is the second part of the message name. As you can see here, message names are split up to help indicate what information you are passing to the receiver. Thus, if I were to message an object myObject with the variables foo and bar, I would type:
  [myObject pickerView:foo numberOfRowsInComponent:bar];
  as opposed to C++ style:
  myObject.pickerView(foo, bar);.

• (NSInteger)component
  This is the last portion of the input. the input here is of type NSInteger and has a local variable name of component.

Hopefully this is helpful!

Objective-C methods are designed to be self documenting, and they borrow from the rich tradition of Smalltalk.

I'll try to explain what you have here, -(NSInteger) pickerView:(UIPickerView*)pickerView numberOfRowsInComponent:(NSInteger)component.

• - (NSInteger)
  This first portion indicates that this is an Objective C instance method that returns a NSInteger object. the - (dash) indicates that this is an instance method, where a + would indicate that this is a class method. The first value in parenthesis is the return value of the method.

• pickerView:
  This portion is a part of the message name. The full message name in this case is pickerView:numberOfRowsInComponent:. The Objective-C runtime takes this method information and sends it to the indicated receiver. In pure C, this would look like
  NSInteger pickerView(UIPickerView* pickerView, NSInteger component). However, since this is Objective-C, additional information is packed into the message name.

• (UIPickerView*)pickerView
  This portion is part of the input. The input here is of type UIPickerView* and has a local variable name of pickerView.

• numberOfRowsInComponent:
  This portion is the second part of the message name. As you can see here, message names are split up to help indicate what information you are passing to the receiver. Thus, if I were to message an object myObject with the variables foo and bar, I would type:
  [myObject pickerView:foo numberOfRowsInComponent:bar];
  as opposed to C++ style:
  myObject.pickerView(foo, bar);.

• (NSInteger)component
  This is the last portion of the input. the input here is of type NSInteger and has a local variable name of component.

Hopefully this is helpful!