On Wed, Jan 10, 2018 at 12:27 PM, Rasmus Lerdorf <ras...@lerdorf.com> wrote:
> If you stay away from trying to change a 25-year old loosely typed > language into a strictly typed one, then the RFC becomes much simpler. > > -Rasmus > I have REPEATEDLY stated that is not the goal. I don't misrepresent what you say, please do not do that to me. I want to see strict typing as an option, not a requirement. Arggh... I said I'd stay away from implementation, but would this work? Working this into z_val in any way is problematic. So, store elsewhere? Create a symbol table that holds the strict variables and the types they are locked into. The strict keyword pushes them onto that table, the var keyword pulls them off. When an operation that cares about type occurs check that table - if the var appears there than authenticate it. I would hope that if a programmer doesn't want strict typing the overhead of checking an empty table would be minimal, even if repeated a great many times.
