>So the internals stay almost the same, but before resorting to die, >you attempt a cast, if it works you warn that's inefficient under strict, >and of course in the docs. If I occasionally want to be inefficient, I should >have the license to do so. But I really don't think it'll be that less >efficient, considering the alternative is to do the casting myself, which will >almost certainly use more memory, and run slower than anything in the core. >No? It will show that you are doing what you *want* to do, not letting automagic error-blind spoofery behind the curtains flummux up your life unnecessarily. --tom
- Re: functions that deal with hash should be m... Tom Christiansen
- Re: functions that deal with hash should ... Casey R. Tweten
- Re: functions that deal with hash sho... Tom Christiansen
- Re: functions that deal with has... Casey R. Tweten
- Re: functions that deal with hash sho... Nathan Torkington
- Re: functions that deal with has... Chaim Frenkel
- Re: functions that deal with hash sho... Jonathan Scott Duff
- Re: functions that deal with hash should be m... John Porter
- Re: functions that deal with hash should ... Casey R. Tweten
- Re: functions that deal with hash should be more liber... Jerrad Pierce
- Re: functions that deal with hash should be more ... Tom Christiansen
- Re: functions that deal with hash should be more liber... Jerrad Pierce
- Re: functions that deal with hash should be more ... Tom Christiansen
- Re: functions that deal with hash should be more ... John Porter
- Re: functions that deal with hash should be more liber... Jerrad Pierce
- Re: functions that deal with hash should be more ... Tom Christiansen