I should like to know people opinions about async interface for user callback functions.
Until now we have 2 different strategies: 1) async:// which uses port/awake with an argument to switch among states 2) call:// which uses port/locals/custom-name1: func [][] port/locals/custom-name2: func [][] Rebol has not a standard method for handling async port call-back, so can be useful to reach an agreement about a pseudo-standard. What do you think? --- Ciao Romano -- To unsubscribe from this list, just send an email to [EMAIL PROTECTED] with unsubscribe as the subject.
