FRINK Linked Data Fragments server

Matches in SemOpenAlex for { <https://semopenalex.org/work/W2076165783> ?p ?o ?g. }

• W2076165783 abstract "It is difficult today to think of machines of the early fifties. A vaguely recollected machine, which probably combines features of more than one real machine, had as memory a rotating drum. The instruction format included an operation code and four addresses. The first three addresses were not unusual: the locations of two operands and the result of the operation. The fourth address was the location of the next instruction. A programmer had to pick a spot on the drum that will be under the read head when the instruction finishes. It required a bit of ingenuity and lots of experimentation to get the most out machines from that era. The job was not made any easier by the fact the machines typically had about a thousand words of storage.It was not long before assemblers and compilers took over the job of managing machine operations. Programs were divided into two major sections: procedures and data. The small storage capacity raised a problem: to store all numbers with the same number of bits required a choice. If the word size was small, precision was limited; if large, relatively few numbers could be stored. A compromise was reached by storing numbers in several different formats that used more storage when greater precision was required. Data-types had arrived.It was to be a several years before the term polymorphism was applied in the computer field. An early use of the word is cited in the OED: The various portraits of her majesty astonish by their perplexing polymorphism… [1839 Fraser's Mag. XX. 699].Compilers in the fifties required a set of declarations that preceded the executable code. The names of variables were classified into groups that specified the storage formats of their respective members. Different instruction sequences were needed to perform arithmetic on differently formatted numbers.Nonnumeric data was a category by itself. Before long nonnumeric subcategories, i. e., data-types, were recognized. Some of them formed nested sequences, just as the early numeric types --- bits, small integers, large integers, and floating point --- formed a natural sequence. The domain of a function was the set of data-types on which it could operate.A typical OOPS requires declaration of the data-types and functions that apply to them in a different way. Instead of considering functions and the data-types that they can accept, it considers data-types and the sets of functions that can use them. As in the case of FORTRAN, declarations must be complete before programming begins. The sets of functions could be thought of as function-types, although the term has been little used, if at all.No matter just how the information on data and function types were stored in the early computer and compiler days, and no matter whether they were stored with the CPU or on disk or drum, not many thought then about arrays of functions. The Michigan Algorithm Decoder (MAD), a compiler of the late fifties, is the only place I know of which supported indexed function name variables." @default.
• W2076165783 created "2016-06-24" @default.
• W2076165783 creator A5055738373 @default.
• W2076165783 date "1998-12-01" @default.
• W2076165783 modified "2023-10-18" @default.
• W2076165783 title "Functions and data can dance as equal partners" @default.
• W2076165783 doi "https://doi.org/10.1145/312627.312705" @default.
• W2076165783 hasPublicationYear "1998" @default.
• W2076165783 type Work @default.
• W2076165783 sameAs 2076165783 @default.
• W2076165783 citedByCount "0" @default.
• W2076165783 crossrefType "proceedings-article" @default.
• W2076165783 hasAuthorship W2076165783A5055738373 @default.
• W2076165783 hasBestOaLocation W20761657831 @default.
• W2076165783 hasConcept C138885662 @default.
• W2076165783 hasConcept C169590947 @default.
• W2076165783 hasConcept C199360897 @default.
• W2076165783 hasConcept C2777904410 @default.
• W2076165783 hasConcept C2778514511 @default.
• W2076165783 hasConcept C33923547 @default.
• W2076165783 hasConcept C41008148 @default.
• W2076165783 hasConcept C41895202 @default.
• W2076165783 hasConcept C50831359 @default.
• W2076165783 hasConcept C55526617 @default.
• W2076165783 hasConcept C90805587 @default.
• W2076165783 hasConcept C9390403 @default.
• W2076165783 hasConcept C94375191 @default.
• W2076165783 hasConceptScore W2076165783C138885662 @default.
• W2076165783 hasConceptScore W2076165783C169590947 @default.
• W2076165783 hasConceptScore W2076165783C199360897 @default.
• W2076165783 hasConceptScore W2076165783C2777904410 @default.
• W2076165783 hasConceptScore W2076165783C2778514511 @default.
• W2076165783 hasConceptScore W2076165783C33923547 @default.
• W2076165783 hasConceptScore W2076165783C41008148 @default.
• W2076165783 hasConceptScore W2076165783C41895202 @default.
• W2076165783 hasConceptScore W2076165783C50831359 @default.
• W2076165783 hasConceptScore W2076165783C55526617 @default.
• W2076165783 hasConceptScore W2076165783C90805587 @default.
• W2076165783 hasConceptScore W2076165783C9390403 @default.
• W2076165783 hasConceptScore W2076165783C94375191 @default.
• W2076165783 hasLocation W20761657831 @default.
• W2076165783 hasOpenAccess W2076165783 @default.
• W2076165783 hasPrimaryLocation W20761657831 @default.
• W2076165783 hasRelatedWork W1497385637 @default.
• W2076165783 hasRelatedWork W1992155208 @default.
• W2076165783 hasRelatedWork W2017090477 @default.
• W2076165783 hasRelatedWork W2040663641 @default.
• W2076165783 hasRelatedWork W2053833907 @default.
• W2076165783 hasRelatedWork W2192862863 @default.
• W2076165783 hasRelatedWork W2289766767 @default.
• W2076165783 hasRelatedWork W2369288331 @default.
• W2076165783 hasRelatedWork W3137189469 @default.
• W2076165783 hasRelatedWork W1482645738 @default.
• W2076165783 isParatext "false" @default.
• W2076165783 isRetracted "false" @default.
• W2076165783 magId "2076165783" @default.
• W2076165783 workType "article" @default.