Matt Youell writes: > As I think about this, however, I can imagine that some might want to force > it's use. Perhaps that requirement could be built into a strict pragma, like > 'use StrictTypes' ?? I seem to recall an RFC along those lines. My idea for use strict 'types'; is that Perl requires variables to be typed, and prevents assignments between incompatible types. A kind of compile-time type checking of the kind that C++ provides. I don't know how Larry's planning to do interfaces, but it's possible that we could even have pluggable type-checking systems: if C++'s inheritance polymorphism peeves you, use something else. I shudder to think of something that prevents simple variable accesses and instead requires verbose method calls. That doesn't seem to be making anything easy. Nat
- Re: RFC 161 (v2) OO Integration/Migration Path Matt Youell
- Re: RFC 161 (v2) OO Integration/Migration Path Nathan Wiger
- Re: RFC 161 (v2) OO Integration/Migration ... Nathan Torkington
- Re: RFC 161 (v2) OO Integration/Migrat... Nathan Wiger
- Re: RFC 161 (v2) OO Integration/Migrat... Randal L. Schwartz
- Re: RFC 161 (v2) OO Integration/M... Nathan Wiger
- Re: RFC 161 (v2) OO Integration/M... Matt Youell
- Re: RFC 161 (v2) OO Integration/Migration ... Matt Youell
- Re: RFC 161 (v2) OO Integration/Migrat... Nathan Wiger
- Re: RFC 161 (v2) OO Integration/Migrat... Bart Lateur
- Re: RFC 161 (v2) OO Integration/Migration Path Nathan Torkington
- Re: RFC 161 (v2) OO Integration/Migration ... Matt Youell
- Re: RFC 161 (v2) OO Integration/Migrat... Nathan Wiger
- Re: RFC 161 (v2) OO Integration/M... Matt Youell
- Re: RFC 161 (v2) OO Integration/Migration Path Nathan Torkington
- Re: RFC 161 (v2) OO Integration/Migration Path Dan Sugalski
- Re: RFC 161 (v2) OO Integration/Migration Path Steve Fink
- Re: RFC 161 (v2) OO Integration/Migration ... Dan Sugalski
- Re: RFC 161 (v2) OO Integration/Migration ... Nathan Wiger
- Re: RFC 161 (v2) OO Integration/Migration Path Nathan Wiger