Swift : missing argument label 'xxx' in call

http://stackoverflow.com/questions/24050844/swift-missing-argument-label-xxx-in-call

up vote 37down votefavorite 10

func say(name:String, msg:String) { println("\(name) say \(msg)") } say("Henry","Hi,Swift") <---- error because missing argument label 'msg' in call I need to use say("Henry",msg:"Hi,Swift") Why ? If I put more than two var in func so that I need to write var name instead of first var when I call this func It's really trouble, and I don't see any explain in iBook Swift tutorial. ios  swift share improve this question edited Jun 9 '14 at 14:58 wolfcastle 3,14811029 asked  Jun 5 '14 at 2:50 henry4343 1,5511817

2   your function name is "say" yet you are calling sayHello?? –  Sam B Jun 5 '14 at 2:56 1   possibly related: stackoverflow.com/questions/24049272/… –  Jiaaro Jun 5 '14 at 2:56 I have been seen this question but it didn't solve my problem –  henry4343 Jun 5 '14 at 3:03 Is this a method? (A function w/in the scope of a class?) –  Logan Jun 5 '14 at 3:17 add a comment

3 Answers

active oldest votes

up vote 44down voteaccepted

One possible reason is that it is actually a method. Methods are very sneaky, they look just like regular functions, but they don't act the same way, let's look at this: func funFunction(someArg: Int, someOtherArg: Int) { println("funFunction: \(someArg) : \(someOtherArg)") } // No external parameter funFunction(1, 4) func externalParamFunction(externalOne internalOne: Int, externalTwo internalTwo: Int) { println("externalParamFunction: \(internalOne) : \(internalTwo)") } // Requires external parameters externalParamFunction(externalOne: 1, externalTwo: 4) func externalInternalShared(#paramOne: Int, #paramTwo: Int) { println("externalInternalShared: \(paramOne) : \(paramTwo)") } // The '#' basically says, you want your internal and external names to be the same externalInternalShared(paramOne: 1, paramTwo: 4) Now here's the fun part, declare a function inside of a class and it's no longer a function ... it's a method class SomeClass { func someClassFunctionWithParamOne(paramOne: Int, paramTwo: Int) { println("someClassFunction: \(paramOne) : \(paramTwo)") } } var someInstance = SomeClass() someInstance.someClassFunctionWithParamOne(1, paramTwo: 4) This is part of the design of behavior for methods Apple Docs: Specifically, Swift gives the first parameter name in a method a local parameter name by default, and gives the second and subsequent parameter names both local and external parameter names by default. This convention matches the typical naming and calling convention you will be familiar with from writing Objective-C methods, and makes for expressive method calls without the need to qualify your parameter names. Notice the autocomplete:  share improve this answer answered  Jun 5 '14 at 4:37 Logan 15.7k62058

Funny how without providing the name for the second parameter in Playground seems to work beautifully! – user1107173 Oct 10 '14 at 4:56 1   @user1107173 - That's because it's out of the context of a class. If you put it inside a class, it would provide the name for the second parameter. Playground doesn't have anything to do with it :) –  Logan Oct 10 '14 at 13:03 add a comment

up vote 6down vote

This is simply an influence of the Objective-C language. When calling a method, the first parameter of a method does not need to be explicitly labelled (as in Objective-C it is effectively 'labelled' by the name of the method). However all following parameters DO need a name to identify them. They may also take an (optional) local name for use inside the method itself (see Jiaaro's link in the comments above). share improve this answer answered  Jun 5 '14 at 3:22 Ephemera 3,18031752

I feel like instead of saying "does not need to be explicitly labeled" we could say "cannot be labeled" because adding a label there will result in a compilation error. –  ShaChris23 Jun 20 '14 at 6:15 add a comment

up vote -1down vote

This is a quirk in the compiler. Functions (which are not members of a class) and class methods have different default behavior with regards to named parameters. This is consistent with the behavior of named parameters in objective-C (but makes no sense for someone new to swift with no experience with objective-C). Here's what the language reference has to say about named parameters for functions (specifically parameters where an external name for the parameter is not given, and the parameter does not have a default value) However, these parameter names are only used within the body of the function itself, and cannotbe used when calling the function. These kinds of parameter names are known as local parameter names, because they are only available for use within the function’s body. For information about class methods, see Logan's answer. share improve this answer edited Sep 9 '14 at 18:06     answered  Jun 5 '14 at 3:39 user3386109 11.9k21227

It's actually not that simple. If you read further into the documentation, there are times when the internal name is automatically turned into an external name, from what I remember it's primarily within class definitions the 2nd and following tags are required by default. –  David Berry Jun 5 '14 at 6:10 2   @David Agreed, my answer covers the case where the func is actually a function. Logan's answer covers the case where the func is actually a method. Personally, I don't like this design choice on Apple's part. The function/method calling syntax should be consistent, regardless of context. Programmers can use the #syntax to force the use of parameter names as a matter of style. –  user3386109 Jun 5 '14 at 6:28 add a comment

转载于:https://www.cnblogs.com/xuejinhui/p/4618502.html