Click here to Skip to main content
14,603,096 members

Welcome to the Lounge

   

For discussing anything related to a software developer's life but is not for programming questions. Got a programming question?

The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
 
GeneralRe: Old age shows its mark... Pin
V.31-Jan-19 19:59
professionalV.31-Jan-19 19:59 
GeneralRe: Old age shows its mark... Pin
Marco Bertschi31-Jan-19 21:44
professionalMarco Bertschi31-Jan-19 21:44 
GeneralRe: Old age shows its mark... Pin
Retired201731-Jan-19 23:22
MemberRetired201731-Jan-19 23:22 
GeneralRe: Old age shows its mark... Pin
Member 79891221-Feb-19 0:58
MemberMember 79891221-Feb-19 0:58 
GeneralRe: Old age shows its mark... Pin
MKJCP1-Feb-19 1:53
MemberMKJCP1-Feb-19 1:53 
GeneralRe: Old age shows its mark... Pin
Member 79891221-Feb-19 2:32
MemberMember 79891221-Feb-19 2:32 
GeneralRe: Old age shows its mark... Pin
MKJCP1-Feb-19 2:42
MemberMKJCP1-Feb-19 2:42 
GeneralRe: Old age shows its mark... Pin
Member 79891221-Feb-19 3:32
MemberMember 79891221-Feb-19 3:32 
In the early 1980s I read an analysis of the time consumption of CDC (mainframe systems) compilers. One of them spent about 60% of the total running time on getting the next source file character to the tokenizer.

In the 35+ years since then I have never learnt anything that could fully explain that figure; maybe they had no buffering at any level between the getc() and the pysical disk. That would be crazy, but how can you explain the observations in other ways? That compiler certainly cannot have spent much resources on, say, fancy optimizations!

The claim has some substance. I worked with Tcl/Tk in the early days, when the source code was directly interpreted: If a loop was executed a million times, the same source code statements were tokenized and parsed a million times. Whitespace and comments were skipped over a million times. Symbols were looked up a million times. So there were preprocessors removing all comments and unneccessary whitespace, to make the code run significantly faster. Some of these preprocessors also replaced longer variable names with short ones, but due to the extremely dynamic nature of Tcl (you can build a character string at run time, and then execute it as a statement - if you build a string referring to a variable name, it wouldn't find the shorter name). When Tcl introduced bytecodes, speed increased by a significant factor.

I have heard similar stories from other developers, using other interpreted languages, and sometimes they argue in favor of short names to speed up interpretation. Today, that is mostly an old myth that won't die: Bytecode compilation, or at least some sort of pre-processing, has become the norm in anything that is called "interpreted" languages. (With no pre-processing, they are commonly called "scripting" languages nowadays.)
GeneralRe: Old age shows its mark... Pin
Bruce Patin1-Feb-19 4:49
MemberBruce Patin1-Feb-19 4:49 
GeneralRe: Old age shows its mark... Pin
Overtkill1-Feb-19 5:06
MemberOvertkill1-Feb-19 5:06 
GeneralRe: Old age shows its mark... Pin
Dr.Walt Fair, PE1-Feb-19 7:03
subeditorDr.Walt Fair, PE1-Feb-19 7:03 
GeneralRe: Old age shows its mark... Pin
Dr.Walt Fair, PE1-Feb-19 8:30
subeditorDr.Walt Fair, PE1-Feb-19 8:30 
GeneralRe: Old age shows its mark... Pin
jschell2-Feb-19 7:12
Memberjschell2-Feb-19 7:12 
GeneralAt the risk of showing my ignorance... Pin
dandy7231-Jan-19 10:11
Memberdandy7231-Jan-19 10:11 
GeneralRe: At the risk of showing my ignorance... Pin
abmv31-Jan-19 16:43
professionalabmv31-Jan-19 16:43 
GeneralRe: At the risk of showing my ignorance... Pin
dandy721-Feb-19 7:10
Memberdandy721-Feb-19 7:10 
GeneralRe: At the risk of showing my ignorance... Pin
abmv1-Feb-19 18:12
professionalabmv1-Feb-19 18:12 
GeneralRe: At the risk of showing my ignorance... Pin
dandy722-Feb-19 2:11
Memberdandy722-Feb-19 2:11 
GeneralRe: At the risk of showing my ignorance... Pin
Fueled By Caffeine31-Jan-19 22:16
MemberFueled By Caffeine31-Jan-19 22:16 
GeneralRe: At the risk of showing my ignorance... Pin
dandy721-Feb-19 7:11
Memberdandy721-Feb-19 7:11 
GeneralRe: At the risk of showing my ignorance... Pin
Dr.Walt Fair, PE1-Feb-19 7:05
subeditorDr.Walt Fair, PE1-Feb-19 7:05 
GeneralRe: At the risk of showing my ignorance... Pin
dandy721-Feb-19 7:13
Memberdandy721-Feb-19 7:13 
GeneralRe: At the risk of showing my ignorance... Pin
Dr.Walt Fair, PE1-Feb-19 8:33
subeditorDr.Walt Fair, PE1-Feb-19 8:33 
GeneralRe: At the risk of showing my ignorance... Pin
jschell2-Feb-19 7:19
Memberjschell2-Feb-19 7:19 
GeneralRe: At the risk of showing my ignorance... Pin
dandy723-Feb-19 6:53
Memberdandy723-Feb-19 6:53 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.