News for hackers. Stuff that matters.

A comment on Why Tcl?. Parent comment

Re:Why Tcl? by tyingq on Tuesday June 20, 2023 @12:33PM (#36406599)
If it's a myth, the myth seems driven by the TCL team itself.

https://wiki.tcl-lang.org/page/everything+is+a+string

Yes, there is some detail about internal dual representation.

[ Parent | on HN ]
Re:Why Tcl? by kevin_thibedeau on Tuesday June 20, 2023 @12:56PM (#36406957)
That wiki page has been around since before Tcl 8. Nobody says lisp is hampered because everything is an S-expr.
[ Parent | on HN ]
Re:Why Tcl? by tyingq on Tuesday June 20, 2023 @01:42PM (#36407625)
> That wiki page has been around since before Tcl 8

Maybe, but it's clearly been updated after Tcl 8. And while the page itself isn't calling it something that hampers tcl, it does cover that it's somewhat unusual, that is has implications, and so on.

[ Parent | on HN ]
Re:Why Tcl? by dkfellows on Friday June 23, 2023 @12:21PM (#36449011)
Technically, all values are considered subtypes of strings, but the notion of types is quite different to those of many other languages. In particular, Tcl's types do not describe the memory storage model of their values. (They're implemented with 64-bit words and buffers and arrays and so on, but that's not what the value model describes.)

It works well as long as your goal isn't to totally eliminate boxing of values.

[ Parent | on HN ]