3 ms·
runtime here means the runtime of target program, it has nothing to do with unix. If your program fails while executing due to a type error, it's not static ty
by xfer 9y ago
runtime here means the runtime of target program, it has nothing to do with unix. If your program fails while executing due to a type error, it's not static type-checking.
- shalabhc 9y agoI think sparkie has a very valid point. It has to do with Unix because a 'program' in Unix has specific meaning (and Windows is no different in this regard, btw). A Unix program doesn't map exactly to what a program means in the theoretical sense. E.g. two Unix processes talking over a socket are not thought of as single Unix program, even though they can be considered a single theoretical program. So there is a tendency to think in 'processes' not 'systems'. I elaborated a little more about this elsewhere in this thread (https://news.ycombinator.com/item?id=15581591 https://news.ycombinator.com/item?id=15581591).
- xfer 9y agoBut it has nothing to with typing, as typing means tying to a location in program, you can have processes communicating part of the same program, but the type-error will refer to a part of program and when the type-error is detected i.e. during execution of that part of program or some external part of program is what we are concerned here. Example: You could think of an interpreter for a statically-typed language running various processes as the same program, but we still say the language is statically typed.
- shalabhc 9y ago> You could think of an interpreter for a statically-typed language running various processes as the same program, but we still say the language is statically typed. Is it statically typed for cross process messages though?