A literal or "appropriate literal" is the value of any given metadata entity that can be either a hyperlink or a string value (literal). A literal affords a great deal of flexibility and power, but increases complexity. Metadata should as well include an appropriate literal that reflects the base value of the metadata entity. For example, in these fragments: creator = "Public, John Q." creator = " http://authority.org/public-john-q-1234" the first has a value expressed as an appropriate literal whereas the second has a (hypothetical) link to an authority structure. It is not entirely clear what a person or application will find at the end of the link, so the metadata should contain an appropriate literal for simple discovery purposes.
An object that can be created by the compiler. A literal can be a number, a character string, a single character, a symbol, or an array. All literals are unique: two literals with the same value refer to the same object. The object created by a literal is read-only: it cannot be changed.
A pure value rather than a named object. 3, 5.6, -8.0 are numerical literals. 'a', 'C' and '\t' are examples of character literals. "Message", "This is a literal" and "\n" are examples of string literals. Note that character literals go in single quotes whereas string literals go in double quotes.
A literal character or string is one that represents itself, that is, that can be taken literally (as opposed to a pattern, that represents some other characters). For a metacharacter to regain its literal value (for example, for to mean an asterisk and not ``zero or more characters'') it must be ``quoted''. See quoting and wildcard.
The most primitive value type represented in RDF, typically a string of characters. The content of a literal is not interpreted by RDF itself and may contain additional XML markup. Literals are distinguished from Resources in that the RDF model does not permit literals to be the subject of a statement.
A literal is a value that is represented "as is" in your source code. There are four types of Perl literals: Number, Strings, Arrays, and Hashes. Chapter 2 "Numeric and String Literals," shows many examples of literals.
Words, letters, numerals, and special characters that are used exactly as they are written. No variable substitution or interpretation is done on literals. An example is anything contained within quotation marks on a PRINT statement.
An error that was made in the original MANUSCRIPT. It is differentiated from a TYPO in that it is generally a grammatical or factual error rather than a slip of the fingers. "Checking for literals", however, is proofreading the words only, ignoring style and layout.
any error in typesetting or word processing of text, usually in incorrect spelling asthead the presentation on the front page of the newspaper's title. Correct term is title piece. Also called a flag oint the standard unit of type size, 12 points to a pica, the basis of print measurement
Compile mode: ( n -- ) Pops the value n from the stack, and compiles it such that it will be pushed at run-time. Interpret mode: ( n -- n ) LITERAL has no effect when INTERPRETING. LITERAL allows certain calculations to be performed once at compile time and stores only the result, along with a run-time operator, LIT, to push the result to the stack. This frees us from having to perform that same calculation repeatedly at run-time just to keep pushing the same value to the stack. NOTE: LITERAL should not be used if the data to be compiled represents the address of a JForth entity. See the discussion of ALITERAL in the CLONE chapter. Standards: fig '79 83 : TEN-DOZEN ( -- ten-dozen ) [ 10 12 * ] LITERAL ; Related Words: [ ] COMPILE IMMEDIATE LIT
adj. (of an object) referenced directly in a program rather than being computed by the program; that is, appearing as data in a quote form, or, if the object is a self-evaluating object, appearing as unquoted data. In the form (cons "one" '("two")), the expressions "one", ("two"), and "two" are literal objects.