> And ghod forbid, for arrays: > > elements PMC, int > > (an elements op would be really nice, because then > infinite lists > could return infinite elements:) > > elements PMC, PMC > > It might be confusing to have both "set elements" > and "get elements" > by the same name. But those are just details.
OK. Took me a while to figure out what you were getting at here: Have get_num_elements and set_num_elements ops instead of having to use get_i_p. This 'guessing what the user meant based on the types he passed in' business is for the birds, though I suppose it cuts down on the size of vtables a bit... :-/ > > And likewise for strings. (At the moment, > > I am forced to use 'set' for strings, because > > assign S0, 23 > > throws a 'can't find assign_s_ic' error.) > > But the set_s_ic op doesn't do an assign. > > S0 = "Hello" > S1 = S0 > S1 = 23 > print S0 > > Prints "Hello". Bah. OK. Thanks for clearing that up :-) - TOGoS __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com
