"...for neither" - really?

[Mark Schonewille]

Don't read, don't write, don't wait for it. Perhaps "for neither" could 
be changed into "without waiting". Definitely not asynchronously, 
because that frightens new users. We should do anything we can to keep 
the language as accessible as possible.

--
Best regards,

Mark Schonewille

Economy-x-Talk Consulting and Software Engineering
Homepage: http://economy-x-talk.com
Twitter: http://twitter.com/xtalkprogrammer
KvK: 50277553

Installer Maker for LiveCode:
http://qery.us/468

Buy my new book "Programming LiveCode for the Real Beginner" 
http://qery.us/3fi

LiveCode on Facebook:
https://www.facebook.com/groups/runrev/

On 7/25/2014 21:34, Richard Gaskin wrote:
> Monte recently helped me with a shell task by reminding me that I can
> use this for asynchronously calling another process:
>
>    open tSomeProcessCommand for neither
>
> Useful enough, but the syntax kinda bugs me.
>
> When you read the full Dictionary entry for "open process" it kinda
> makes sense, but it feels a bit silly to type it.
>
> Anyone here think it's worth the dev team's time to propose
> "asynchronously" as a synonym for "for neither"?
>
> Better still, anyone here know their way around the code base and care
> enough about this sort of nit-picking to add that?
>
> Is it even worth thinking about?
>