Your suggestion makes it harder to read for those less familiar with the /sockread command and it's switches, IMO. They'll see /sockread but the -t32 will have them scratching their heads. I doubt you know what every switch for every command does. I know I don't. Good code should be easy to understand even if you aren't an expert at it. The command /sockread tells that it does a socket read, but -t32 tells you nothing and is something that has to be looked up.
Yes my way is just a different way of the same thing you suggested. Identifiers are added all the time, and it is for a good reason. The one you suggested, provide a simpler way of tokenizing the incoming socket string.
Last edited by MeStinkBAD; 19/07/15 02:55 AM.
