I just spoke to Marc about the refactorings. He suggests keeping the array/string methods global, and then assigning them on the Array/String prototype object. We could then hide the global methods (make them invisible to the user) with Tachyon-specific annotations. This would make it possible to guarantee that these methods are always accessible, even if the user redefines them on the prototype object. It could also make it possible to make them call each other statically, if the said methods need to call one another.
I think we might also perhaps want to add some kind of global variable that only exists when compilation occurs under Tachyon. This would allow the array and string implementations to use conditional tests (eg: if (TACHYON_JSVM !== undefined)) to change their implementation depending on whether they're running on V8 or Tachyon.
- Maxime
Whenever works for you :) Sooner is probably better.
- Maxime
On 2011-02-03, at 12:12 , chevalma@iro.umontreal.ca wrote:
Hello Marc & Bruno,
I'd like to start integrating your stdlib code into Tachyon and testing it out with the primitives we have. However, this might require some (fairly minor?) refactorings.
If you have time, could you come by the lab today or tomorrow afternoon so I can tell you what I have in mind and discuss integration into the Tachyon runtime?
I'm available today until 3:30 or tomorrow all afternoon. What works best for you?
-b_______________________________________________ Tachyon-list mailing list Tachyon-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/tachyon-list
Tachyon-list mailing list Tachyon-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/tachyon-list