From ... From: Erik Naggum Subject: Re: Reply to Ousterhout's reply (was Re: Ousterhout and Tcl ...) Date: 1997/04/18 Message-ID: <3070390128524499@naggum.no>#1/1 X-Deja-AN: 235876485 References: <5ihaol$n3g@Masala.CC.UH.EDU> <5ilnmp$rg9@engnews2.Eng.Sun.COM> <334EDC93.2376@maths.anu.edu.au> <5it19k$n8k@m1.cs.man.ac.uk> <3353200E.52CD@maths.anu.edu.au> <5j0gq5$jbi@mimsy.cs.umd.edu> <3070209881177993@naggum.no> <5j5o3a$9rn@mimsy.cs.umd.edu> <3070347275198364@naggum.no> <5j8ice$agv@mimsy.cs.umd.edu> mail-copies-to: never Organization: Naggum Software; +47 2295 0313; http://www.naggum.no Newsgroups: comp.lang.scheme,comp.lang.scheme.scsh,comp.lang.lisp,comp.lang.tcl,comp.lang.functional,comp.lang.c++,comp.lang.perl.misc,comp.lang.python,comp.lang.eiffel * Charles Lin | Now, perhaps I completely misunderstood what Ousterhout did, but I was | under the impression that he said everything in Tcl (the external | representation) is a string. Why are we talking about internal | representations at all? because the internal representation in Tcl is the string. | Internal representations aren't going to be important because they are | hidden from the user (mostly). I think you're missing the point all over the place. Tcl's purpose is to glue different applications together, but also to do something with the returned "values" (i.e., output) of these programs. of course we're dealing with interfaces where external representations will be used, but Tcl uses the same external representations for internal purposes, too. when you execute a numeric operation, the string is converted to a number, the operation is performed, and then converted back to a string. in contrast to this view, AWK converts a string to a number when it is used for a numeric purpose, and a number to a string when it is used for a string purpose, but not otherwise. (at least, this is what I have understood from what I have read about Tcl.) | The point is that (almost) no one wants to write a program whose | *external* representation is numbers. nobody has suggested they do, and nobody in their right mind would. | Strings are more flexible, if they're the only type you have, as external | representation. but external representations _aren't_ typed! I'd venture that that's the whole point in using an _untyped_ string (or even byte-sequence) representation is that whoever reads it would be able to interpret it, indeed that type would emerge from the interpretation. #\Erik -- I'm no longer young enough to know everything.