From: SourceForge.net <no...@so...> - 2007-06-29 01:47:19
|
Bugs item #1731572, was opened at 2007-06-05 13:22 Message generated for change (Comment added) made by chad3f You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101111&aid=1731572&group_id=1111 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 9 Private: No Submitted By: Miguel Angel Blanch Lardin (arianne_rpg) Assigned to: Miguel Angel Blanch Lardin (arianne_rpg) Summary: Marauroa: Can't use same name for attrib and slot Initial Comment: That's plainly wrong. ---------------------------------------------------------------------- >Comment By: ChadF (chad3f) Date: 2007-06-28 21:47 Message: Logged In: YES user_id=1668474 Originator: NO Why is this wrong? Aside from a few languages (like perl), this is the norm. Personally, I'd rather think of a slot/link as just another attribute.. only instead of a string or int, it's an object container (slot) or another object (link). By allowing name overloading, it might complicate later possibilties. For example, if some form of simple scripting language is ever added (maybe for client enhancement, and/or interactive adhoc server objects), one would need to use special symbols to type the field. Assuming a javascript like syntax was used, would 'x = player.foo' copy the foo attribute, slot, or link (assuming all coexisted in player)? I will admit that overloaded names would provide some convenience (when transitioning fields), but in general it just seems likely to add confusion. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101111&aid=1731572&group_id=1111 |