From: SourceForge.net <no...@so...> - 2007-06-12 15:12:56
|
Feature Requests item #1734213, was opened at 2007-06-09 17:27 Message generated for change (Comment added) made by bigrixx You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684733&aid=1734213&group_id=119701 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: Classes Group: Next Release >Status: Pending >Resolution: Rejected Priority: 5 Private: No Submitted By: Rony G. Flatscher (orexx) Assigned to: Nobody/Anonymous (nobody) Summary: Please allow argument on Collection classes 'NEW' Initial Comment: Working with the new features of the collection classes and experimenting with putAll and a supplier the utility of creating different collection class renderings can be enhanced, if the 'NEW' method of the collection classes accepted an optional argument, either a collection or a supplier (and in the case of ordered or set collections any object that possesses a MAKEARRAY method). The generic INIT-code for the collection classes could look like: ------------ cut here ------------ ::METHOD INIT use strict arg initialItems=.nil if arg(1, "E") then do if self~isA(.OrderedCollection) then self~appendAll(initialItems) else self~putAll(initialItems) end ------------ cut here ------------ This would ease coding for the purpose of rendering a collection or supplier to a specific collection at creation time. E.g. m=.array~methods /* get a supplier */ r=.relation~new(m) /* create a relation, add the supplier index/item pairs to it */ Alternatively (already possible) one could code the same as: m=.array~methods /* get a supplier */ r=.relation~new /* create a relation */ r~putAll(m) /* add the supplier index/item pairs to it */ ---------------------------------------------------------------------- >Comment By: Rick McGuire (bigrixx) Date: 2007-06-12 11:12 Message: Logged In: YES user_id=1125291 Originator: NO This is not a good idea, as it will make it difficult and awkward to extend the new method to add additional options to the collections in the future. For example, adding initial capacity and expansion strategy options to table, et al would be a good future enhancement. This feature overlaps with function already available to the particular collections, so it doesn't really add any capability while at the same time creates additional complications for the future. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684733&aid=1734213&group_id=119701 |