On 3 Sep 2010 06:39:47 -0700, [email protected] (McKown, John) wrote:
>One of the many reasons that I prefer computer languages. They are not >ambiguous. >Well, they shouldn't be. I guess you could design one where the meaning of a >statement >is not defined unambiguously. But it is definately implemented unambiguously. >Hum, or >is that true? I've heard of cases where the semantics of a user written >program changed >due to a change in a compiler or the use of a different version of the >compiler. <sign> But we have to work with some very basic terms that can be ambiguous without the proper context. At the top of this list are "debit & credit". When we put signs on debits and credits, and when we share the results with users (as in "debit card", where the meaning is mirrored left to right), ambiguity requires proper documentation. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
