First ask him/her for an email address, and then while you are over the phone send the text by email. This way the other can *instantaneously* read and both of you can talk about the code.
On Fri, Oct 16, 2009 at 1:01 PM, Ashley Sheridan <a...@ashleysheridan.co.uk>wrote: > On Fri, 2009-10-16 at 18:01 +0200, Dotan Cohen wrote: > > > > Wow! Here goes: > > > > > > Open-bracket, dollar item hypen greater-than, get service id, no all > one word but with a capital S and I. Open and close brackets, question mark, > dollar item again, then a hyphen and greater-than, that get service id and > brackets bit again, exactly the same as last time; yes, capital S and I > again. Colon, no the colon is the one with two dots, not dot and comma. > Dollar item again, then hypen, greater-than, get id, with a capital I. Nope, > no service bit this time. Now, open bracket and two closing brackets (I > assumed the final two on your example were typos?!). now a semi-colon, yes > the one with the comma. > > > > > > That's pretty much how I could foresee me telling someone this on the > phone, but to be honest, I'd really prefer an email ;) > > > > > > > So it really involves mentioning each character. I was hoping that > > there would be a shared language for constructs such as -> and the > > like. > > > > Thanks. > > > > -- > > Dotan Cohen > > > > http://what-is-what.com > > http://gibberish.co.il > > > Not that I know of, and trying to explain any sort of code over the > phone is just going to lead to a disaster down the line! > > Thanks, > Ash > http://www.ashleysheridan.co.uk > > > -- Martin Scotta