Le 27 nov. 07 à 07:55, Ian Piumarta a écrit :
Or have the data transform itself, dynamically, according to how it's
being used? A single 'collection' type that occasionally internally
reorganises itself (or employs other mechanisms for optimising a
subset of the possible operations into constant time) as an array,
stack, queue, list, dequeue, set, bag, (some kind of) tree, stream,
etc., depending how you're using it at the moment. This is, I think,
a hard problem and one well worth solving.
one of the "self" paper talks about that:
Organizing Programs Without Classes, Ungar, Chambers, Chang and
Höllze. LISP AND SYMBOLIC COMPUTATION: An International Journal, 4,
3, 1991
actually, this is one advantage of using prototypes, as it can modify
its "class" at run-time, and use optimized structure during one
particular context.
> Time is wasted on removing unnecessary whitespace
> and programmers seem to constantly clean up code because it doesn't
> comply to the style guidelines (I've seen lots of commits in
Haiku ala
> "style cleanup").
[...]
> I've often heard experienced
> programmers say that they've come to realize that code
readability is
> the most important thing because you have to spend a lot of time
> understanding other people's code, esp. when joining a new team.
I think you might have just addressed your own complaint. ;-)
That's why I would like to help where and when I can (not with code,
but mostly with creating a good interaction model and UI). Let me
know
if you're interested.
Of course!
Cheers,
Ian
_______________________________________________
fonc mailing list
[email protected]
http://vpri.org/mailman/listinfo/fonc
Stéphane Conversy
Enseignant Chercheur en IHM - ENAC
http://lii-enac.fr/~conversy
enac: +33 5 62 17 40 19
dgac r&d: +33 5 62 25 96 48
_______________________________________________
fonc mailing list
[email protected]
http://vpri.org/mailman/listinfo/fonc
