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=-0.5 required=5.0 tests=BAYES_00,INVALID_MSGID, PP_MIME_FAKE_ASCII_TEXT autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII X-Google-Thread: fac41,b87849933931bc93 X-Google-Attributes: gidfac41,public X-Google-Thread: 109fba,b87849933931bc93 X-Google-Attributes: gid109fba,public X-Google-Thread: 103376,b87849933931bc93 X-Google-Attributes: gid103376,public X-Google-Thread: f43e6,b87849933931bc93 X-Google-Attributes: gidf43e6,public X-Google-Thread: 1108a1,b87849933931bc93 X-Google-Attributes: gid1108a1,public X-Google-Thread: 114809,b87849933931bc93 X-Google-Attributes: gid114809,public From: "Vos nom et pr�nom" Subject: Re: What is wrong with OO ? Date: 1997/01/14 Message-ID: <01bbd235$b0f3fbe0$LocalHost@christophe-leph>#1/1 X-Deja-AN: 209950161 references: <5acjtn$5uj@news3.digex.net> <32D11FD3.41C6@wi.leidenuniv.nl> <32D53473.4DAA423A@eiffel.com> organization: Chris & Co newsgroups: comp.lang.c++,comp.lang.smalltalk,comp.lang.eiffel,comp.lang.ada,comp.object,comp.software-eng Date: 1997-01-14T00:00:00+00:00 List-Id: Piercarlo Grandi a �crit dans l'article ... > >>> "bertrand" == Bertrand Meyer writes: > > bertrand> The ISE Eiffel compiler performs inlining completely > bertrand> automatically. There is no "pragma inline" or comparable > bertrand> programmer intervention, since it is not the programmer's job > bertrand> to worry about whether a routine is inlinable or not. This is > bertrand> a job for a compiler. > > It seems contrary to reasonabless: there are many contexts where > inlining is not necessary and others in which it is important, *even for > the same procedure*. Thus there is (usually) a space/time tradeoff, but > *at each call site*. It sounds astonishing to me an argument that the > compiler should try to second guess or infer space/time tradeoffs > (except perhaps in the simplest cases), in addition to doing its job of > compiling valid translations of a source. etc... Here's my 2cts... If the function is very short, it's obvious for the compiler to automatically inline it. When it's long, it's also obvious not to make it inline. But where is the point where the short function becomes a long function ? For all these cases, it's the programmer's responsability to inline or not regarding size vs speed. -- Chris "The nail pulling up calls the hammer" zen proverb