Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

Support methods with no type information #147

Open
cgriffin opened this Issue · 1 comment

2 participants

@cgriffin

On line 29 of GBMethodArgument is the following code:

NSParameterAssert(([types count] == 0 && var == nil) || ([types count] > 0 && var != nil));

This assert was failing on my project. I traced it to a missing argument type declaration. In one of my .m files. I had something like this:

```- (void)myMethod:(NSObject *)obj anotherObject:aObject { }

The method declaration was correct in the .h file however. Now why the compiler did complain I don't know. So there is actually a valid situation where the assert above would fail. Depending on you definition of "valid". :) The feature would be to spit out the file and line number where this occurred to help the user find the issue.
@tomaz
Owner

Your case is valid objective-c method declaration, as you've deducted. appledoc currently requires type info (for no particular reason, it just simplified coding and I think it's good practice to keep type in method declaration too). And nobody complained (up until now :)). Will mark this as bug and see how much work it would require to make it optional.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.