[Wesnoth-bugs] [patch #1045] is_set variable condition

Update of patch #1045 (project wesnoth): Open/Closed:Open => Closed ___ Reply to this item at: ___ Nachricht

[Wesnoth-bugs] [patch #1045] is_set variable condition

Follow-up Comment #9, patch #1045 (project wesnoth): It sounds like the person who worked on the Tutorial had a bug in their code and was simply confused. This method of testing for empty string works fine: [variable] name=foo equals=$empty [/variable] This method had problems in the past (

[Wesnoth-bugs] [patch #1045] is_set variable condition

Follow-up Comment #8, patch #1045 (project wesnoth): Except that unset (cleared) variable *does not* reset to an empty string (0) or does not allways behave like this. I don't know why, but if you wan't an example there is one in 1st sceanrio of the tutorial. Quoting : #FIXME: You'd think that u

[Wesnoth-bugs] [patch #1045] is_set variable condition

Update of patch #1045 (project wesnoth): Status:None => Wont Do ___ Follow-up Comment #7: well, our WML experts seem to agree that it isn't really a good idea, so i'll mark as "won't d

[Wesnoth-bugs] [patch #1045] is_set variable condition

Follow-up Comment #6, patch #1045 (project wesnoth): Yes, even though I wouldn't mind having an unique test for whether a variable exists or not, I agree with sapient's points about the scalar and array problem and that any addition like this should not break the current behaviour. I think it's

[Wesnoth-bugs] [patch #1045] is_set variable condition

Follow-up Comment #5, patch #1045 (project wesnoth): quick discussion with zookeeper, he seems to agree with sapient.. it there a way to turn this into something usefull ? i.e that would false if the var doesn't exit or is "" or is 0 etc... __

[Wesnoth-bugs] [patch #1045] is_set variable condition

Follow-up Comment #4, patch #1045 (project wesnoth): Another point to consider: since arrays and scalars do not share the same namespace, I could have a container named "foo" and yet is_set for "foo" would return false. This ambiguity is another reason I am against introducing this feature.

[Wesnoth-bugs] [patch #1045] is_set variable condition

Follow-up Comment #3, patch #1045 (project wesnoth): I really don't see the need for this. All unset variables in WML are string equivalent to empty string, numerically equivalent to zero, and boolean equivalent to false. Making a distinction between "set" and "unset" doesn't grant any real capab

[Wesnoth-bugs] [patch #1045] is_set variable condition

Follow-up Comment #2, patch #1045 (project wesnoth): Done (file #4147) ___ Additional Item Attachment: File name: isset2.patch Size:2 KB ___ Reply to this item a

[Wesnoth-bugs] [patch #1045] is_set variable condition

Update of patch #1045 (project wesnoth): Assigned to:None => boucman ___ Follow-up Comment #1: looks good, just a minor comment * you did not add yourself in the "contributor" section of d

[Wesnoth-bugs] [patch #1045] is_set variable condition

URL: Summary: is_set variable condition Project: Battle for Wesnoth Submitted by: elfy Submitted on: Saturday 04/05/2008 at 13:32 Priority: 3 - Low Status: None