Talk:ASH Errors

Is this like were things like Script parsing error (X.ash, line Y) are listed?--Icon315 22:33, 14 April 2010 (UTC)

It's where they WILL be listed, once they are listed. --Bale 22:52, 14 April 2010 (UTC)

What Bale said. Also, I changed that to orange; I kept trying to click on it. :( --StDoodle (#1059825) 00:35, 15 April 2010 (UTC)

Also, if anyone's feeling particularly ambitious, https://kolmafia.svn.sourceforge.net/svnroot/kolmafia/src/net/sourceforge/kolmafia/textui/Parser.java should help. Just look for all the instances of parseException. (Speaking of which, would it be useful if these were presented in the order that they're checked?) --Heeheehee 00:17, 17 April 2010 (UTC)

I think alphabetical order would be better: this page is going to be excellent for first-time ASH scripters to understand what's wrong with their script. --Slyz 10:41, 17 April 2010 (UTC)

Should we add the correct examples? Or are the fixes clear enough? --Slyz 08:36, 18 April 2010 (UTC)

If anything particularly complicated shows, we can give both. But so far, if you can't follow as written, I'm not sure you ever will. (That's the hypothetical "you," not the specific "hey Slyz what's wrong with you, you"). --StDoodle (#1059825) 23:35, 19 April 2010 (UTC)

The following code results in an error.

void my_function( string myvar = "value" )
{
   /* Do something */
}

Error message:

Cannot initialize parameter myvar (filename.ash, line X)

I'd like to add this to the article myself, but I'm not sure how to explain its exact nature. Would this message appear only in a situation like the above code? --PhilmASTErpLus 09:30, 28 July 2010 (UTC)

Looks like a conflict of functionality -- the two ways to initialize a variable are string myvar and string myvar = "value". The only proper way to define a parameter is the former. So basically you're defining a parameter, which then gets initialized with a value. This would lead to all sorts of problems, so the parser catches this exception and throws an error. I'm not really sure why anyone would want to do this, but I guess you can add it? (fun fact: the value that you set the parameter to doesn't actually have to match the datatype for this error to appear) --Heeheehee 16:47, 28 July 2010 (UTC)

I'm guessing he tried it for the same reason I did; in some languages, that's how you provide a default value for a parameter. It's usually functionally equivalent to having two different versions of my_function() defined, one which accepts a single string, and one which accepts no parameters, and calls the other with the default value. Usually it isn't a big deal to do things one way or the other, but the method given above can actually be much simpler if you get into a large number of overloaded versions of a single function. --StDoodle (#1059825) 18:30, 28 July 2010 (UTC)

In that case, would this be a reasonable low-priority feature request? --Heeheehee 18:44, 28 July 2010 (UTC)

That's up to the devs, but I have a feeling it would be a non-trivial change to get a trivial benefit, and therefore ignored. Unless someone has a good argument for a situation in which it would make a huge difference. --StDoodle (#1059825) 21:08, 28 July 2010 (UTC)

Hardly worth suggesting. The KoLmafia method works just fine:

void my_function()
{
   my_function("value");
}

--Bale 04:31, 29 July 2010 (UTC)

Yeah, when I posted that code, I wasn't thinking about requesting for a default parameter feature. All I'd like to know is whether there is a general case that will trigger this particular error message; for example, I would have expected this instead of "expected ) but got =" message when I tried assignment in the conditional for the if and while statements. --PhilmASTErpLus 13:17, 29 July 2010 (UTC)