User talk:PhilmASTErpLus - Revision history

StDoodle at 01:43, 28 September 2010

2010-09-28T01:43:03Z

← Older revision		Revision as of 01:43, 28 September 2010
Line 17:		Line 17:

	I like the ASH Quirks and Hacks section on your page. I did not know that stuff and I thought that I knew a good bit about ash. I feel that should definitely be added to some page on the wiki or given it's own page though I'm not sure where it would be best to add it. --[[User:Bale\|Bale]] 05:19, 13 September 2010 (UTC)		I like the ASH Quirks and Hacks section on your page. I did not know that stuff and I thought that I knew a good bit about ash. I feel that should definitely be added to some page on the wiki or given it's own page though I'm not sure where it would be best to add it. --[[User:Bale\|Bale]] 05:19, 13 September 2010 (UTC)

			== Headings ==

			For some reason, I was under the impression that there weren't adequate styles for h4 level headings, which is why I redid that page as I did (also, it was a last-minute hectic change to provide info to a specific user). I would prefer if page titles were done differently on the wiki, such that they weren't headings. However, that's an unreasonable level of customization, so you're right, we should avoid h1 (except if we need to do special overrides of page titles) and go from there. We should probably agree on & post this in a guideline / help page somewhere, but for reference, it's very important not to "skip" levels. If we find that h2 also looks bad, that should be dealt with by altering the stylesheets for the wiki, not by avoiding that level of heading. Good catch. --[[User:StDoodle\|StDoodle (#1059825)]] 01:43, 28 September 2010 (UTC)

Bale: ASH Quirks and Hacks

2010-09-13T05:19:17Z

ASH Quirks and Hacks

← Older revision		Revision as of 05:19, 13 September 2010
Line 13:		Line 13:

	Edit by JasonHarper moved to [[Talk:ASH For Beginners]]		Edit by JasonHarper moved to [[Talk:ASH For Beginners]]

			== ASH Quirks and Hacks ==

			I like the ASH Quirks and Hacks section on your page. I did not know that stuff and I thought that I knew a good bit about ash. I feel that should definitely be added to some page on the wiki or given it's own page though I'm not sure where it would be best to add it. --[[User:Bale\|Bale]] 05:19, 13 September 2010 (UTC)

StDoodle: /* ASH For Beginners */

2010-07-27T11:16:19Z

ASH For Beginners

← Older revision		Revision as of 11:16, 27 July 2010
Line 12:		Line 12:
	== [[ASH For Beginners]] ==		== [[ASH For Beginners]] ==

	~~Your recent edit is completely wrong; I would have reverted it, except that the reason field wasn't big enough to explain just how it was wrong.~~		Edit by JasonHarper moved to [[Talk:ASH For Beginners]]

	~~ALL values in ASH are passed and assigned in a completely uniform manner, regardless of type. That manner could either be referred to as "call by value" or "call~~ by ~~reference"; the two concepts aren't distinct here, since all ASH values are references to some object. No copying is ever done, except as part of an implicit type conversion.~~

	You appear to be confusing the concepts of call type and mutability. There's no difference in how (for example) a map and an int value are passed; the observed differences in behavior are entirely due to the fact that there are ways to modify the contents of a map (with it still remaining the same map), yet no ways of modifying the value of an integer. The closest you can come is to produce a new integer value, and assign it to ~~the same variable that formerly held the old value; it is the variable that is changing, not the value. --~~[[~~User~~:~~Jasonharper\|Jasonharper~~]] ~~05:49, 27 July 2010 (UTC)~~

Jasonharper: /* ASH For Beginners */ new section

2010-07-27T05:49:33Z

ASH For Beginners: new section

← Older revision		Revision as of 05:49, 27 July 2010
Line 9:		Line 9:

	Browsing through the function pages, I found this: {{f\|to_string}} (see the source for template details) --[[User:Heeheehee\|Heeheehee]] 19:03, 4 July 2010 (UTC)		Browsing through the function pages, I found this: {{f\|to_string}} (see the source for template details) --[[User:Heeheehee\|Heeheehee]] 19:03, 4 July 2010 (UTC)

			== [[ASH For Beginners]] ==

			Your recent edit is completely wrong; I would have reverted it, except that the reason field wasn't big enough to explain just how it was wrong.

			ALL values in ASH are passed and assigned in a completely uniform manner, regardless of type. That manner could either be referred to as "call by value" or "call by reference"; the two concepts aren't distinct here, since all ASH values are references to some object. No copying is ever done, except as part of an implicit type conversion.

			You appear to be confusing the concepts of call type and mutability. There's no difference in how (for example) a map and an int value are passed; the observed differences in behavior are entirely due to the fact that there are ways to modify the contents of a map (with it still remaining the same map), yet no ways of modifying the value of an integer. The closest you can come is to produce a new integer value, and assign it to the same variable that formerly held the old value; it is the variable that is changing, not the value. --[[User:Jasonharper\|Jasonharper]] 05:49, 27 July 2010 (UTC)

Heeheehee: Faster way to make inline function links

2010-07-04T19:03:25Z

Faster way to make inline function links

← Older revision		Revision as of 19:03, 4 July 2010
Line 6:		Line 6:

	Regarding your recent user page update -- the ideal place to put such information, I think, is probably [[file_to_map]]. Also, there should probably be a little blurb on that page mentioning that you don't need those files in your data directory (they're built into the jars), but having them present will override the built-in mapfiles. --[[User:Heeheehee\|Heeheehee]] 23:58, 1 July 2010 (UTC)		Regarding your recent user page update -- the ideal place to put such information, I think, is probably [[file_to_map]]. Also, there should probably be a little blurb on that page mentioning that you don't need those files in your data directory (they're built into the jars), but having them present will override the built-in mapfiles. --[[User:Heeheehee\|Heeheehee]] 23:58, 1 July 2010 (UTC)


			Browsing through the function pages, I found this: {{f\|to_string}} (see the source for template details) --[[User:Heeheehee\|Heeheehee]] 19:03, 4 July 2010 (UTC)

Heeheehee at 23:58, 1 July 2010

2010-07-01T23:58:23Z

← Older revision		Revision as of 23:58, 1 July 2010
Line 3:		Line 3:

	I was not aware of this either; we'll need to see where that means we need to make changes. --[[User:StDoodle\|StDoodle (#1059825)]] 05:07, 22 June 2010 (UTC)		I was not aware of this either; we'll need to see where that means we need to make changes. --[[User:StDoodle\|StDoodle (#1059825)]] 05:07, 22 June 2010 (UTC)


			Regarding your recent user page update -- the ideal place to put such information, I think, is probably [[file_to_map]]. Also, there should probably be a little blurb on that page mentioning that you don't need those files in your data directory (they're built into the jars), but having them present will override the built-in mapfiles. --[[User:Heeheehee\|Heeheehee]] 23:58, 1 July 2010 (UTC)

StDoodle at 05:07, 22 June 2010

2010-06-22T05:07:55Z

← Older revision		Revision as of 05:07, 22 June 2010
Line 1:		Line 1:
	"aggregate" and "map" are NOT synonyms. "aggregate" is an abstract type; the three concrete implementations of that type are maps, arrays, and plural typed constants (which require a separate implementation because they need to be immutable). --[[User:Jasonharper\|Jasonharper]] 04:36, 22 June 2010 (UTC)		"aggregate" and "map" are NOT synonyms. "aggregate" is an abstract type; the three concrete implementations of that type are maps, arrays, and plural typed constants (which require a separate implementation because they need to be immutable). --[[User:Jasonharper\|Jasonharper]] 04:36, 22 June 2010 (UTC)
	:Uh-huh. Sorry about that editing rampage, should I go and revert them? Or how about alternatives? --[[User:PhilmASTErpLus\|PhilmASTErpLus]] 04:39, 22 June 2010 (UTC)		:Uh-huh. Sorry about that editing rampage, should I go and revert them? Or how about alternatives? --[[User:PhilmASTErpLus\|PhilmASTErpLus]] 04:39, 22 June 2010 (UTC)

			I was not aware of this either; we'll need to see where that means we need to make changes. --[[User:StDoodle\|StDoodle (#1059825)]] 05:07, 22 June 2010 (UTC)

PhilmASTErpLus at 04:39, 22 June 2010

2010-06-22T04:39:06Z

← Older revision		Revision as of 04:39, 22 June 2010
Line 1:		Line 1:
	"aggregate" and "map" are NOT synonyms. "aggregate" is an abstract type; the three concrete implementations of that type are maps, arrays, and plural typed constants (which require a separate implementation because they need to be immutable). --[[User:Jasonharper\|Jasonharper]] 04:36, 22 June 2010 (UTC)		"aggregate" and "map" are NOT synonyms. "aggregate" is an abstract type; the three concrete implementations of that type are maps, arrays, and plural typed constants (which require a separate implementation because they need to be immutable). --[[User:Jasonharper\|Jasonharper]] 04:36, 22 June 2010 (UTC)
			:Uh-huh. Sorry about that editing rampage, should I go and revert them? Or how about alternatives? --[[User:PhilmASTErpLus\|PhilmASTErpLus]] 04:39, 22 June 2010 (UTC)

Jasonharper: Created page with '"aggregate" and "map" are NOT synonyms. "aggregate" is an abstract type; the three concrete implementations of that type are maps, arrays, and plural typed constants (which requ…'

2010-06-22T04:36:06Z

Created page with '"aggregate" and "map" are NOT synonyms. "aggregate" is an abstract type; the three concrete implementations of that type are maps, arrays, and plural typed constants (which requ…'

New page

"aggregate" and "map" are NOT synonyms. "aggregate" is an abstract type; the three concrete implementations of that type are maps, arrays, and plural typed constants (which require a separate implementation because they need to be immutable). --[[User:Jasonharper|Jasonharper]] 04:36, 22 June 2010 (UTC)