000 | 01186nab a22002537 4500 | ||
---|---|---|---|
001 | H004.415 JOU | ||
003 | AR-sfUTN | ||
008 | 190909b xx |||p|r|||| 00| 0 spa d | ||
040 | _cAR-sfUTN | ||
080 | _aH004.415 JOU | ||
100 | _aMeyer, Bertrand | ||
245 | _aOverloading vs. object technology | ||
336 |
_2rdacontent _atexto _btxt |
||
337 |
_2rdamedia _asin mediaciĆ³n _bn |
||
338 |
_2rdacarrier _avolumen _bnc |
||
505 | _aThis convention, "saying nothing means new plus a warning," seems to be an effort at addressing a minor potential problem by causing major potential damage. How real is the minor problem anyway? If one of your classes inherits from A and you get a new version of A, it would be very foolish to accept the new version blindly; you should check that it does not affect the assumptions that your class made about its parents | ||
650 | _aSYSTEMS DEVELOPMENT | ||
650 | _aMETHODS | ||
650 | _aSYSTEMS MANAGEMENT | ||
650 | _aOBJECT ORIENTED PROGRAMMING | ||
773 |
_tJOOP : the journal of object-oriented programming _wH004.415 JOU _nS.T.:H004.415 JOU PP3436 _g(vol. 14, nro. 4, Oct-Nov. 2001), p. 3-7 |
||
942 | _cAN | ||
999 |
_c37451 _d37451 |