I keep getting this error: bad argument definition in four lines of my coding. i dont know how to fix it per say. How do i fix this
Jan 11 2016, 1:31 pm
|
|
Developer Help is the right place for this. You'll also have to show the lines of code where the errors are in order for us to help you fix it.
|
should i just take this to developer help then?
and oops, i thought i posted it. returnif(subinvis) pretty much the 1st line and the last line |
Try putting your code in between tags. It'll make it show up properly:
<DM> CODE GOES HERE </DM> Also, the code you posted doesn't give me enough information to go on. I'll need to see the lines that are actually affected by the error. |
In response to MegaJkeezy
|
|
MegaJkeezy wrote:
I did, i said the 1st line and the last line Could you post your code properly in DM tags? Also, again, I don't have enough information to go on. The errors do not appear to be related to the first and last lines of what you posted. |
>>return Coding\1.4.Verbs.dm:830:error: bad argument definition Coding\1.4.Verbs.dm:861:error: bad argument definition Coding\1.4.Verbs.dm:861:error: bad argument definition Coding\1.4.Verbs.dm:861:error: bad argument definition those are the errors. The line numbers represent the first and last line. I dont know how much more information you want |
In response to MegaJkeezy
|
|
MegaJkeezy wrote:
> >>return Coding\1.4.Verbs.dm:830:error: bad argument definition He wants the entire proc, from the point where you would have said:
whatever/proc/thingy(arg1,arg2,...,argn)
or whatever/verb/thingy(arg1 as anything,arg2 as anything,arg3 as anything) all the way to the very last line of the same procedure. As in, he wants the ENTIRE thing, not just what you deem relevant. EDIT: I'm gonna word the last sentence in a less condescending way: He wants all of it, not just what's between those two lines, so everything in the proc before and after those lines needs to be posted. |
Oh sorry about that, bad misunderstanding on my end.
//attack |
...Could you please, for the love of all that is holy mark the lines where the errors are pointing? Please only show me the function that is relevant to the problem. I didn't want the entire file. I want the whole proc that has the errors in it, and I want the lines where the errors are pointing clearly marked with comments. |
check the edit
I gave you the whole proc. didnt give you the whole file. That one comment is the whole proc. If i would have gave the whole file, it would be way longer than that. lines #830 and #861 is marked. |
Found it. You can't name a proc throw() anymore it's a built in keyword now. You'll have to change the name of the throw() command across your entire codebase.
Also, I think that return is tabbed back two spaces too far. |
Alright, thank you. Would you happen to know the new name then?
|
Would you happen to know the new name then? That's something you need to decide. |