Talk:ASH Errors - Revision history

StDoodle at 16:30, 29 July 2010

2010-07-29T16:30:21Z

← Older revision		Revision as of 16:30, 29 July 2010
Line 14:		Line 14:
	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"). --[[User:StDoodle\|StDoodle (#1059825)]] 23:35, 19 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"). --[[User:StDoodle\|StDoodle (#1059825)]] 23:35, 19 April 2010 (UTC)

			==Cannot initialize parameter...==

	{{CodeSample\|description=The following code results in an error.		{{CodeSample\|description=The following code results in an error.
Line 43:		Line 43:
	: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 <code>if</code> and <code>while</code> statements. --[[User:PhilmASTErpLus\|PhilmASTErpLus]] 13:17, 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 <code>if</code> and <code>while</code> statements. --[[User:PhilmASTErpLus\|PhilmASTErpLus]] 13:17, 29 July 2010 (UTC)
	:Bale -- I know that works nicely, but in the event that there are ten overloaded forms of one function, I might want to save a bit on typing (or copy-pasting, as the case so often happens to be). --[[User:Heeheehee\|Heeheehee]] 14:45, 29 July 2010 (UTC)		:Bale -- I know that works nicely, but in the event that there are ten overloaded forms of one function, I might want to save a bit on typing (or copy-pasting, as the case so often happens to be). --[[User:Heeheehee\|Heeheehee]] 14:45, 29 July 2010 (UTC)

			To Phil; can't see as to how this particular error would crop up elsewhere; I'm guessing it had to be purposefully set as (part of) a special check for parameters in a function. Regarding the "which way to do default values" debate, I'd rather that was continued on the forum if at all, as none of us are in a position to make a change without the devs giving the go ahead first. But as mentioned earlier, I doubt it will be given much thought unless a compelling use-case can be thought of that isn't possible under the current setup. --[[User:StDoodle\|StDoodle (#1059825)]] 16:30, 29 July 2010 (UTC)

Heeheehee at 14:45, 29 July 2010

2010-07-29T14:45:14Z

← Older revision		Revision as of 14:45, 29 July 2010
Line 42:		Line 42:
	--[[User:Bale\|Bale]] 04:31, 29 July 2010 (UTC)		--[[User:Bale\|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 <code>if</code> and <code>while</code> statements. --[[User:PhilmASTErpLus\|PhilmASTErpLus]] 13:17, 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 <code>if</code> and <code>while</code> statements. --[[User:PhilmASTErpLus\|PhilmASTErpLus]] 13:17, 29 July 2010 (UTC)
			:Bale -- I know that works nicely, but in the event that there are ten overloaded forms of one function, I might want to save a bit on typing (or copy-pasting, as the case so often happens to be). --[[User:Heeheehee\|Heeheehee]] 14:45, 29 July 2010 (UTC)

PhilmASTErpLus: Thanks for input, but does anyone know whether there exists other forms of code that can cause this error?

2010-07-29T13:17:55Z

Thanks for input, but does anyone know whether there exists other forms of code that can cause this error?

← Older revision		Revision as of 13:17, 29 July 2010
Line 41:		Line 41:
	</syntaxhighlight>}}		</syntaxhighlight>}}
	--[[User:Bale\|Bale]] 04:31, 29 July 2010 (UTC)		--[[User:Bale\|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 <code>if</code> and <code>while</code> statements. --[[User:PhilmASTErpLus\|PhilmASTErpLus]] 13:17, 29 July 2010 (UTC)

Bale at 04:31, 29 July 2010

2010-07-29T04:31:30Z

← Older revision		Revision as of 04:31, 29 July 2010
Line 31:		Line 31:

	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. --[[User:StDoodle\|StDoodle (#1059825)]] 21:08, 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. --[[User:StDoodle\|StDoodle (#1059825)]] 21:08, 28 July 2010 (UTC)


			{{CodeSample\|description=Hardly worth suggesting. The KoLmafia method works just fine:
			\|code=<syntaxhighlight>
			void my_function()
			{
			my_function("value");
			}
			</syntaxhighlight>}}
			--[[User:Bale\|Bale]] 04:31, 29 July 2010 (UTC)

StDoodle at 21:08, 28 July 2010

2010-07-28T21:08:36Z

← Older revision		Revision as of 21:08, 28 July 2010
Line 29:		Line 29:
	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. --[[User:StDoodle\|StDoodle (#1059825)]] 18:30, 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. --[[User:StDoodle\|StDoodle (#1059825)]] 18:30, 28 July 2010 (UTC)
	: In that case, would this be a reasonable low-priority feature request? --[[User:Heeheehee\|Heeheehee]] 18:44, 28 July 2010 (UTC)		: In that case, would this be a reasonable low-priority feature request? --[[User:Heeheehee\|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. --[[User:StDoodle\|StDoodle (#1059825)]] 21:08, 28 July 2010 (UTC)

Heeheehee at 18:44, 28 July 2010

2010-07-28T18:44:10Z

← Older revision		Revision as of 18:44, 28 July 2010
Line 28:		Line 28:

	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. --[[User:StDoodle\|StDoodle (#1059825)]] 18:30, 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. --[[User:StDoodle\|StDoodle (#1059825)]] 18:30, 28 July 2010 (UTC)
			: In that case, would this be a reasonable low-priority feature request? --[[User:Heeheehee\|Heeheehee]] 18:44, 28 July 2010 (UTC)

StDoodle at 18:30, 28 July 2010

2010-07-28T18:30:27Z

← Older revision		Revision as of 18:30, 28 July 2010
Line 26:		Line 26:
	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? --[[User:PhilmASTErpLus\|PhilmASTErpLus]] 09:30, 28 July 2010 (UTC)		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? --[[User:PhilmASTErpLus\|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) --[[User:Heeheehee\|Heeheehee]] 16:47, 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) --[[User:Heeheehee\|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. --[[User:StDoodle\|StDoodle (#1059825)]] 18:30, 28 July 2010 (UTC)

Heeheehee at 16:47, 28 July 2010

2010-07-28T16:47:07Z

← Older revision		Revision as of 16:47, 28 July 2010
Line 25:		Line 25:
	Error message: <blockquote>Cannot initialize parameter myvar (filename.ash, line X)</blockquote>		Error message: <blockquote>Cannot initialize parameter myvar (filename.ash, line X)</blockquote>
	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? --[[User:PhilmASTErpLus\|PhilmASTErpLus]] 09:30, 28 July 2010 (UTC)		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? --[[User:PhilmASTErpLus\|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) --[[User:Heeheehee\|Heeheehee]] 16:47, 28 July 2010 (UTC)

PhilmASTErpLus at 09:35, 28 July 2010

2010-07-28T09:35:14Z

← Older revision		Revision as of 09:35, 28 July 2010
Line 23:		Line 23:
	}		}
	</syntaxhighlight>}}		</syntaxhighlight>}}
	Error message: <blockquote>Cannot initialize parameter myvar (filename.ash, line X)</blockquote> --[[User:PhilmASTErpLus\|PhilmASTErpLus]] 09:30, 28 July 2010 (UTC)		Error message: <blockquote>Cannot initialize parameter myvar (filename.ash, line X)</blockquote>
			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? --[[User:PhilmASTErpLus\|PhilmASTErpLus]] 09:30, 28 July 2010 (UTC)

PhilmASTErpLus at 09:31, 28 July 2010

2010-07-28T09:31:04Z

← Older revision		Revision as of 09:31, 28 July 2010
Line 16:		Line 16:


	{{CodeSample\|code=<syntaxhighlight>		{{CodeSample\|description=The following code results in an error.
			\|code=<syntaxhighlight>
	void my_function( string myvar = "value" )		void my_function( string myvar = "value" )
	{		{
Line 22:		Line 23:
	}		}
	</syntaxhighlight>}}		</syntaxhighlight>}}
	~~Results in an error~~ message: <blockquote>Cannot initialize parameter myvar (filename.ash, line X)</blockquote> --[[User:PhilmASTErpLus\|PhilmASTErpLus]] 09:30, 28 July 2010 (UTC)		Error message: <blockquote>Cannot initialize parameter myvar (filename.ash, line X)</blockquote> --[[User:PhilmASTErpLus\|PhilmASTErpLus]] 09:30, 28 July 2010 (UTC)

← Older revision		Revision as of 16:30, 29 July 2010
Line 14:		Line 14:
	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"). --[[User:StDoodle\|StDoodle (#1059825)]] 23:35, 19 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"). --[[User:StDoodle\|StDoodle (#1059825)]] 23:35, 19 April 2010 (UTC)

			==Cannot initialize parameter...==

	{{CodeSample\|description=The following code results in an error.		{{CodeSample\|description=The following code results in an error.
Line 43:		Line 43:
	: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 <code>if</code> and <code>while</code> statements. --[[User:PhilmASTErpLus\|PhilmASTErpLus]] 13:17, 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 <code>if</code> and <code>while</code> statements. --[[User:PhilmASTErpLus\|PhilmASTErpLus]] 13:17, 29 July 2010 (UTC)
	:Bale -- I know that works nicely, but in the event that there are ten overloaded forms of one function, I might want to save a bit on typing (or copy-pasting, as the case so often happens to be). --[[User:Heeheehee\|Heeheehee]] 14:45, 29 July 2010 (UTC)		:Bale -- I know that works nicely, but in the event that there are ten overloaded forms of one function, I might want to save a bit on typing (or copy-pasting, as the case so often happens to be). --[[User:Heeheehee\|Heeheehee]] 14:45, 29 July 2010 (UTC)

			To Phil; can't see as to how this particular error would crop up elsewhere; I'm guessing it had to be purposefully set as (part of) a special check for parameters in a function. Regarding the "which way to do default values" debate, I'd rather that was continued on the forum if at all, as none of us are in a position to make a change without the devs giving the go ahead first. But as mentioned earlier, I doubt it will be given much thought unless a compelling use-case can be thought of that isn't possible under the current setup. --[[User:StDoodle\|StDoodle (#1059825)]] 16:30, 29 July 2010 (UTC)

← Older revision		Revision as of 14:45, 29 July 2010
Line 42:		Line 42:
	--[[User:Bale\|Bale]] 04:31, 29 July 2010 (UTC)		--[[User:Bale\|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 <code>if</code> and <code>while</code> statements. --[[User:PhilmASTErpLus\|PhilmASTErpLus]] 13:17, 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 <code>if</code> and <code>while</code> statements. --[[User:PhilmASTErpLus\|PhilmASTErpLus]] 13:17, 29 July 2010 (UTC)
			:Bale -- I know that works nicely, but in the event that there are ten overloaded forms of one function, I might want to save a bit on typing (or copy-pasting, as the case so often happens to be). --[[User:Heeheehee\|Heeheehee]] 14:45, 29 July 2010 (UTC)

← Older revision		Revision as of 21:08, 28 July 2010
Line 29:		Line 29:
	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. --[[User:StDoodle\|StDoodle (#1059825)]] 18:30, 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. --[[User:StDoodle\|StDoodle (#1059825)]] 18:30, 28 July 2010 (UTC)
	: In that case, would this be a reasonable low-priority feature request? --[[User:Heeheehee\|Heeheehee]] 18:44, 28 July 2010 (UTC)		: In that case, would this be a reasonable low-priority feature request? --[[User:Heeheehee\|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. --[[User:StDoodle\|StDoodle (#1059825)]] 21:08, 28 July 2010 (UTC)

← Older revision		Revision as of 18:30, 28 July 2010
Line 26:		Line 26:
	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? --[[User:PhilmASTErpLus\|PhilmASTErpLus]] 09:30, 28 July 2010 (UTC)		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? --[[User:PhilmASTErpLus\|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) --[[User:Heeheehee\|Heeheehee]] 16:47, 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) --[[User:Heeheehee\|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. --[[User:StDoodle\|StDoodle (#1059825)]] 18:30, 28 July 2010 (UTC)