|
EssaysAs Knuth pointed out long ago, speed only matters in certain critical bottlenecks. And as many programmers have observed since, one is very often mistaken about where these bottlenecks are. So, in practice, the way to get fast code is to have a very good profiler, rather than by, say, making the language strongly typed. You don't need to know the type of every argument in every call in the program. You do need to be able to declare the types of arguments in the bottlenecks. And even more, you need to be able to find out where the bottlenecks are. One complaint people have had with Lisp is that it's hard to tell what's expensive. This might be true. It might also be inevitable, if you want to have a very abstract language. And in any case I think good profiling would go a long way toward fixing the problem: you'd soon learn what was expensive. Part of the problem here is social. Language designers like to write fast compilers. That's how they measure their skill. They think of the profiler as an add-on, at best ...» |
Код для вставки книги в блог HTML
phpBB
текст
|
|
(499) 213 04 22
Сейф-книга "Alparaisa СС0023/1" (карта первооткрывателей). 
Набор столовый детский "Юниор" (2 предмета). 
Стул для школьника регулируемый Polini City / Polini Smart L (цвет: белый/серый). 
Orthomol Immun Junior Сила иммунитета на страже Вашего ребенка 
