From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 109fba,b87849933931bc93 X-Google-Attributes: gid109fba,public X-Google-Thread: 1108a1,b87849933931bc93 X-Google-Attributes: gid1108a1,public X-Google-Thread: fac41,b87849933931bc93 X-Google-Attributes: gidfac41,public X-Google-Thread: 114809,b87849933931bc93 X-Google-Attributes: gid114809,public X-Google-Thread: f43e6,b87849933931bc93 X-Google-Attributes: gidf43e6,public X-Google-Thread: 103376,b87849933931bc93 X-Google-Attributes: gid103376,public From: Chris.Bitmead@Alcatel.com.au (Chris Bitmead) Subject: Re: What is wrong with OO ? Date: 1997/01/23 Message-ID: #1/1 X-Deja-AN: 211633098 distribution: inet references: <5acjtn$5uj@news3.digex.net> cc: bertrand@eiffel.com organization: Alcatel Australia Limited reply-to: Chris.Bitmead@Alcatel.com.au newsgroups: comp.lang.c++,comp.lang.smalltalk,comp.lang.eiffel,comp.lang.ada,comp.object,comp.software-eng Date: 1997-01-23T00:00:00+00:00 List-Id: In article <32D53473.4DAA423A@eiffel.com> Bertrand Meyer writes: >ISE Eiffel does give the user a degree of parameterization: >a compilation option specifies the size threshold beyond which >a routine will not be inlined. This is measured in internal units >(number of bytecode words), but easy to relate to number of >instructions. This option provides a way to control space-time >tradeoffs. In practice, however, most users are happy with the >default, which inlines small, frequently called routines. How on earth does the compiler know if a routine is "frequently called"?