Risto Vaarandi wrote: > In order to overcome this ambiguity, I've been thinking about adding > event2 action to SEC action set that would have the following syntax: > > event2 <time> [<event text>] > > 'event2' would be identical to 'event', except <time> parameter is > mandatory and may contain other symbols than numerals (0-9) only. > > Note that there is also another option - drop the idea of having 'event2 > <variable_time> <event_text>', and use > > create <context> <variable_time> (event <event_text>) > > instead. In other words, when variable lifetimes are allowed for > contexts, 'event2' can be actually expressed through 'create'. > > Any ideas?
I like the idea of an additional event, but the name itself 'event2' may confuse some. Maybe something like 'tevent' for 'timed event' would work. I definitely think the event2/tevent is much cleaner than the create context workaround you gave for an example. -- -dave ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Simple-evcorr-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/simple-evcorr-users
