Talk:RDF:Interfaces: Difference between revisions

battle star visit
No edit summary
(battle star visit)
 
Line 34: Line 34:
I'll take a mental note.
I'll take a mental note.


== visit return type ==


Enn: rdfITripleVisitor.visit should just return true or false to continue iterating rather than using an incomprehsible system of error codes. In fact, I don't even know how I would get such a return code from JS.
Enn: rdfITripleVisitor.visit should just return true or false to continue iterating rather than using an incomprehsible system of error codes. In fact, I don't even know how I would get such a return code from JS.
Line 46: Line 47:


Enn: huh? The goal is to make the lesser used C++ less cumbersome yet make the more common JS usage more cumbersome? That makes no sense.
Enn: huh? The goal is to make the lesser used C++ less cumbersome yet make the more common JS usage more cumbersome? That makes no sense.
Well, most of the time, the visit code will not bother about iteration, isn't a "you have to return true to make it work" more cumbersome? I don't like the idea of having two ways of stopping iterations, either, as you could still throw an exception or return false. I'm really not digging that. --[[User:AxelHecht|AxelHecht]] 08:00, 16 Jun 2005 (PDT)
Confirmed users, Bureaucrats and Sysops emeriti
2,976

edits