Eric Smith wrote: >>> 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 had the same doubts about the naming -- adding a number doesn't make >> the name descriptive enough) --, but 'tevent' looks a nice choice ;) > > Why make it cryptic at all? Why not "timedevent", or "timed_event"? > "tevent" doesn't have much intrinsic meaning, to me. It's not like > there's a cost to making it readable. > > Eric. >
Most of current action names are rather short, just around 5-6 characters. In fact, the longest ones are 'shellcmd' and 'obsolete', both having a length of just 8 bytes. In my opinion, short names are rather handy - they are concise and when rule files get larger, editing them takes less time. br, risto ------------------------------------------------------------------------- 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
