Mailing List Archive: 49091 messages
  • Home
  • Script library
  • AltME Archive
  • Mailing list
  • Articles Index
  • Site search

[REBOL] Re: COLLECTing results

From: maximo:meteorstudios at: 28-Jul-2003 10:40

> -----Original Message----- > From: Robert M. Muench [mailto:[robert--muench--robertmuench--de]] > > If you think about it, it is this way in REBOL too. It's just > > that we can't make custom datatypes. > > Not only. Do we have all those STL algorithms done in a way, that > supports the generic approach of the STL? I don't think so. > What I would > like to have is: > > Foreach btree-datatype [...] > Foreach skip-list [...] >
true, but its Really easy to overide most functions as an example, I've often rebuilt the print to handle different datatypes differently. my current print, actualy prints out object! as: "first obj", so instead of having a list which runs for 15 minutes (cause it prints out all functions), it gives me a 2-3 line output. I agree with gabrielle, though, that custom dataypes are high on my list of wanted features too. And they would add greatly to the usefullness of the system. the other thing I really would like to get are more hooks within the parser itself. the ability to insert code just before a get and set call in python is genial. This lets you create virtuall methods and attributes... for example in liquid right now, I want to build an object to liquid mapper... well I just can't do it transparently because the moment I do object/attribute: value, I overwrite the function that was set at the place of the attribute, which is supposed to send a message to the liquid. in python, I could have added a little hook before the set, which causes my code to actually set the attribute, instead of the default code. that code would then call a liquid notification of the pipe set to the attribute. Externally, the object still remains an object, but internally, the object behaves quite differently. just my 0.02 -MAx