
	Where results make sense

Topic: X3J13

	X3J13 - Wikipedia, the free encyclopedia
		X3J13 is the name of the Ansi Common Lisp standard technical committee.
		Working files for the X3J13 Ansi Common Lisp committee
		This page was last modified 13:40, 22 March 2006.
	en.wikipedia.org /wiki/X3J13 (53 words)

	[No title]
		X3J13 was criticized by OMC for being somewhat lax in its procedures during 1995, with memberships briefly lapsing and some loss of officers.
		X3J13 has continued to serve as liaison to SC22/WG16, which is preparing an international standard for a dialect of Lisp called ISLISP.
		X3J13 responded to OMC criticisms of its handling of policies and procedures (too few paid members, no meeting in 1995) by bringing membership dues up to appropriate levels (5 paid members) and by holding an annual meeting (1-Jul-96).
	www.ncits.org /minutes/9807ncits/x3960527.htm (1071 words)

	Preface SECOND EDITION (Site not responding. Last check: 2007-10-12)
		X3J13 has completed the bulk of its technical work in rectifying the 1984 definition and codifying extensions to that definition that have received widespread use and approval.
		X3J13, in the course of its work, formed a subcommittee to study whether additional means of iteration should be standardized for use in Common Lisp, for a great deal of existing practice in this area was not included in the first edition because of lack of agreement in 1984.
		X3J13 expressed interest in the other two approaches (series and generators), but the consensus as of January 1989 was that these other approaches were not yet sufficiently mature or in sufficiently widespread use to warrant inclusion in the draft Common Lisp standard at that time.
	www.cs.brandeis.edu /~cs35a/cltl/clm/node2.html (1562 words)

	23.1.6. Pathname Functions (Site not responding. Last check: 2007-10-12)
		X3J13 voted in March 1988 (PATHNAME-SYMBOL) to change the language so that a symbol is never allowed as a pathname argument.
		X3J13 voted in March 1988 not to permit symbols as pathnames (PATHNAME-SYMBOL) and to specify exactly which streams may be used as pathnames (PATHNAME-STREAM) .
		X3J13 voted in January 1989 (CLOSED-STREAM-OPERATIONS) to specify that these operations are unaffected by whether the first argument, if a stream, is open or closed.
	www.cs.brandeis.edu /~cs35a/cltl/clm/node214.html (2754 words)

	X3J13 Charter (Site not responding. Last check: 2007-10-12)
		I am personally very thankful to Susan for her efforts in making sure we did this, since many had at the time opined that it was a waste of time and it might well not have ended up done without her prodding.
		X3J13 DRAFT Purposes Doc: X3J13/86-020 for consideration at March 1987 meeting Purposes of X3J13 Committee (Proposed) 1.
		X3J13 is chartered to produce an American National Standard for Common Lisp.
	www.nhplace.com /kent/CL/x3j13-86-020.html (498 words)

	25.1. The Compiler (Site not responding. Last check: 2007-10-12)
		X3J13 voted in March 1988 (PATHNAME-STREAM) to specify exactly which streams may be used as pathnames (see section 23.1.6).
		X3J13 voted in March 1989 (LOAD-TIME-EVAL) to add a mechanism for delaying evaluation of a form until it can be done in the run-time environment.
		X3J13 voted in January 1989 (FUNCTION-DEFINITION) to add a new function to allow the source code for a defined function to be recovered.
	www.cs.buffalo.edu /~dearman/cse305/cltl/clm/node224.html (2233 words)

	25.1.4. Similarity of Constants
		X3J13 voted in March 1989 (CONSTANT-COMPILABLE-TYPES) to specify what objects can be in compiled constants and what relationship there must be between a constant passed to the compiler and the one that is established by compiling it and then loading its file.
		X3J13 voted in March 1989 (CONSTANT-COLLAPSING) to specify the circumstances under which constants may be coalesced in compiled code.
		X3J13 voted in March 1989 (CONSTANT-CIRCULAR-COMPILATION) to specify that objects containing circular or infinitely recursive references may legitimately appear as constants to be compiled.
	www.oopweb.com /LISP/Documents/cltl/Volume/node228.html (1265 words)

	[No title]
		Jon L White, chairman of the X3J13 Iteration Subcommittee, supervised the consideration of several controversial proposals, one of which (loop) was eventually adopted by X3J13.
		Kathy Chapman, chairwoman of the X3J13 Drafting Subcommittee, and principal author of the draft standard, has not only written a great deal of text but also insisted on coherent and consistent terminology and pushed the rest of the committee forward when necessary.
		Mary Van Deusen, secretary of X3J13, kept excellent minutes that were a tremendous aid to me in tracing the history of a number of complex discussions.
	www.barzilay.org /books/cltl/CLtL-text (16319 words)

	comp
		X3J13 efforts included technical and international activity, not an effort for the US policy alone.
		There is a perception that the Common Lisp Group, and later X3J13, excluded international participation, I believe this is not true.
		X3J13 got involved more by the introduction of the discussion on the Lisp1/Lisp2 issue.
	www.international-lisp-conference.org /2002/Speakers/People/Masayuki-Ida.html (243 words)

	9.1. Declaration Syntax
		X3J13 voted in March 1988 (DECLARE-MACROS) to eliminate the recognition of a declaration resulting from the expansion of a macro call.
		X3J13 voted in January 1989 (SPECIAL-TYPE-SHADOWING) to clarify that such shadowing does not occur in the case of type declarations.
		If there is a local type declaration for a special variable and there is also a global proclamation for that same variable, then the value of the variable within the scope of the local declaration must be a member of the intersection of the two declared types.
	alcor.concordia.ca /~smw/home/cltl/clm/node104.html (1854 words)

	4.5. Type Specifiers That Specialize
		X3J13 voted in January 1989 (ARRAY-TYPE-ELEMENT-TYPE-SEMANTICS) to eliminate the differing treatment of types when used ``for discrimination'' rather than ``for declaration'' on the grounds that implementors have not treated the distinction consistently and (which is more important) users have found the distinction confusing.
		X3J13 also voted in January 1989 (DECLARE-ARRAY-TYPE-ELEMENT-REFERENCES) to specify that within the lexical scope of an array type declaration, it is an error for an array element, when referenced, not to be of the exact declared element type.
		The keyword must be a valid keyword-name symbol that may be supplied in the actual arguments of a call to the function, and the type specifier indicates the permitted type of the corresponding argument value.
	alcor.concordia.ca /~smw/home/cltl/clm/node49.html (1899 words)

	[No title]
		It was plain from the uses in the text throughout the document that there was an ambiguity of meaning that was widespread.
		Inserted a third paragraph: %% Added per Boyer/Kaufmann/Moore #14 (by X3J13 vote at May 4-5, 1994 meeting) %% -kmp 9-May-94 Float substitutability applies neither to the rational \term{functions} \funref{+}, \funref{-}, \funref{*}, and \funref{/} nor to the related \term{operators} \funref{1+}, \funref{1-}, \macref{incf}, \macref{decf}, and \funref{conjugate}.
		Document X3J13/94-309.\cr 05-May-94 & X3J13 & Editorial-only changes to Draft 14.10 in response to comments.\cr 10-May-94 & Pitman & Draft {\rev} (for X3 consideration).
	www.cs.cmu.edu /afs/cs.cmu.edu/project/gwydion-5/hackers/clisp-hackers/ram/work/clman/Change-Summary.text (2614 words)

	21.2. Creating New Streams (Site not responding. Last check: 2007-10-12)
		X3J13 voted in January 1989 (STREAM-ACCESS) to specify that the result of
		X3J13 explicitly noted that the bidirectional streams that are the initial values of
		X3J13 voted in October 1988 (WITH-OUTPUT-TO-STRING-APPEND-STYLE) to specify that if string is specified, it must be a string with a fill pointer; the output is incrementally appended to the string (as if by use of
	www.cs.csubak.edu /~donna/cs350/Code/Lisp/cltl/clm/node184.html (1206 words)

	Implementation
		X3J13, the ANSI subcommittee chartered to propose a specification for the forthcoming ANSI Common Lisp, has voted to make several changes to Common Lisp's treatment of characters.
		Allegro CL 5.0 is an implementation of Common Lisp as specified by the ANSI X3J13 committee.
		X3J13 made a number of improvements to the package system in order to facilitate portability and to regularize the handling of top-level forms in a file.
	www.bu.edu /cc/support/software/programming/lisp/allegro/implementation.htm (4846 words)

	7.2. Generalized Variables (Site not responding. Last check: 2007-10-12)
		X3J13 voted in March 1989 (FUNCTION-NAME) to clarify that this rule applies only when the function name refers to a global function definition and not to a locally defined function or macro.
		X3J13 voted in March 1989 (FUNCTION-NAME) to clarify that this rule applies only when the function name in the form refers to a global function definition and not to a locally defined function or macro.
		X3J13 voted in March 1988 (FLET-IMPLICIT-BLOCK) to specify that the body of the expander function defined by the complex form of
	10.pins1.xdsl.nauticom.net /bvds/cltl/clm/node80.html (5573 words)

	22.1.6. What the Print Function Produces (Site not responding. Last check: 2007-10-12)
		X3J13 voted in June 1989 (READ-CASE-SENSITIVITY) to specify that the new
		X3J13 voted in January 1989 (PRETTY-PRINT-INTERFACE) to adopt a facility for user-controlled pretty printing in Common Lisp (see chapter 27).
		X3J13 voted in January 1989 (PRINT-CIRCLE-STRUCTURE) to specify that user-defined printing functions for the
	library.n0i.net /programming/lisp/co_lisp/clm/node193.html (4089 words)

	25.3. Debugging Tools
		X3J13 voted in January 1989 (ROOM-DEFAULT-ARGUMENT) to specify that the argument x may also be the keyword
		The means by which the function text is obtained is implementation-dependent; it might involve searching the file system, or pretty printing resident interpreted code, for example.
		The vote by X3J13 was an explicit decision not to decide which model to use.
	www.ida.liu.se /imported/cltl/clm/node230.html (1714 words)

	11.7. Package System Functions and Variables
		X3J13 voted in March 1989 (IN-PACKAGE-FUNCTIONALITY) to cancel the specifications of the preceding paragraph in order to support a model of file compilation in which the compiler need never take special note of ordinary function calls; only special forms and macros are recognized as affecting the state of the compilation process.
		X3J13 voted in January 1989 (PACKAGE-DELETION) to add a function to delete packages.
		X3J13 voted in January 1989 (PACKAGE-FUNCTION-CONSISTENCY) to clarify that the package argument may be either a package object or a package name (see section 11.2).
	www.ndsu.nodak.edu /instruct/juell/cs724s01/manuals/cltl/clm/node118.html (5001 words)

	24.2. Specialized Error-Signaling Forms and Macros
		X3J13 voted in June 1988 (CONDITION-SYSTEM) to adopt a proposal for a Common Lisp Condition System.
		X3J13 voted in March 1988 (PUSH-EVALUATION-ORDER) to clarify order of evaluation (see section 7.2).
		X3J13 voted in June 1989 (SETF-MULTIPLE-STORE-VARIABLES) to extend the specification of
	www.oopweb.com /LISP/Documents/cltl/Volume/node221.html (709 words)

	9.2. Declaration Specifiers (Site not responding. Last check: 2007-10-12)
		X3J13 voted in January 1989 (DECLARE-TYPE-FREE) to alter the interpretation of type declarations.
		X3J13 noted that if nested type declarations refer to the same variable, then all of them have effect; the value of the variable must be a member of the intersection of the declared types.
		X3J13 voted in October 1988 (PROCLAIM-INLINE-WHERE) to clarify that during compilation the
	library.n0i.net /programming/lisp/co_lisp/clm/node105.html (3429 words)

	[No title] (Site not responding. Last check: 2007-10-12)
		11 May 94 Dear Reader, At the present time, pending X3J13 vote, this draft (version 15.17, document X3J13/94-101) is an internal draft of the X3J13 committee.
		X3J13 will be asked by letter ballot whether it would like this version forwarded to X3 and OMC for approval.
		It is hoped that X3J13 will vote YES, but we will not know for sure until the letter ballot occurs.
	www.cs.cmu.edu /afs/cs.cmu.edu/project/clisp/OldFiles/hackers/ram/work/clman/Reviewer-Notes.text (323 words)

	23.3. Renaming, Deleting, and Other File Operations (Site not responding. Last check: 2007-10-12)
		It is left to the discretion of the implementation whether an attempt to delete a non-existent file is considered to be successful.
		X3J13 voted in March 1988 (PATHNAME-STREAM) to specify exactly which streams may be used as pathnames.
		However, X3J13 further commented that the treatment of open streams may differ considerably from one implementation to another; for example, in some operating systems open files are written under a temporary or invisible name and later renamed when closed.
	www.aic.uniovi.es /Libros/cltl2e/node216.html (1085 words)

	18.3. String Construction and Manipulation (Site not responding. Last check: 2007-10-12)
		X3J13 voted in January 1989 (ARGUMENTS-UNDERSPECIFIED) to clarify that the size argument must be a non-negative integer less than the value of
		If no characters need to be trimmed from the string, then either the argument string itself or a copy of it may be returned, at the discretion of the implementation.
		X3J13 voted in June 1989 (STRING-COERCION) to specify that the following functions perform coercion on their string arguments identical to that performed by the function
	www.plg.inf.uc3m.es /~docweb/cltl/clm/node167.html (858 words)

	8.2. Macro Expansion (Site not responding. Last check: 2007-10-12)
		X3J13 voted in June 1988 (FUNCTION-TYPE) to specify that the value of
		X3J13 voted in March 1989 (MACRO-ENVIRONMENT-EXTENT) to specify that macro environment objects received by a
		Caching by table lookup won't work because such a table would have to be keyed by both the macro-call form and the environment, but X3J13 voted in March 1989 (MACRO-ENVIRONMENT-EXTENT) to permit macro environments to have only dynamic extent.
	turing.ubishops.ca /cltl/clm/node99.html (596 words)

	2.15. Overlap, Inclusion, and Disjointness of Types
		X3J13 voted in June 1988 (DATA-TYPES-HIERARCHY-UNDERSPECIFIED) to extend the preceding paragraph as follows.
		X3J13 voted in March 1989 (REAL-NUMBER-TYPE) to rewrite the preceding item as follows.
		This is purposely avoided here in order to permit compatible experimentation with extensions to the Common Lisp integer number system, such as the idea of adding explicit representations of infinity or of positive and negative infinity.
	www.ceng.metu.edu.tr /docs/clm/node42.html (735 words)

	23.4. Loading Files (Site not responding. Last check: 2007-10-12)
		If a binary file is being loaded, then what is printed may not reflect precisely the contents of the source file, but nevertheless some information will be printed.
		X3J13 voted in March 1988 (PATHNAME-STREAM) to specify exactly which streams may be used as pathnames.
		X3J13 voted in June 1989 (PATHNAME-WILD) to clarify that supplying a wild pathname as the filename argument to
	www.cs.buffalo.edu /~dearman/cse305/cltl/clm/node217.html (1856 words)

	29. Conditions (Site not responding. Last check: 2007-10-12)
		X3J13 voted in June 1988 (CONDITION-SYSTEM) to adopt the Common Lisp Condition System as a part of the forthcoming draft Common Lisp standard.
		X3J13 voted in March 1989 (ZLOS-CONDITIONS) to amend the specification of conditions to integrate them with the Common Lisp Object System (see chapter 28).
		X3J13 voted in June 1989 (CONDITION-RESTARTS) to amend the specification of restarts in certain ways.
	www.csie.ntu.edu.tw /~ai/2002spring/doc.clisp/cltl/clm/node312.html (243 words)

	19.2. How to Use Defstruct (Site not responding. Last check: 2007-10-12)
		X3J13 voted in October 1988 (DEFSTRUCT-DEFAULT-VALUE-EVALUATION) to clarify that a default-init form is evaluated only if the corresponding argument is not supplied to the constructor function.
		X3J13 voted in January 1989 (DEFSTRUCT-SLOTS-CONSTRAINTS-NAME) to specify that it is an error for two slots to have the same name; more precisely, no two slots may have names for whose print names
		The problem is that if instances have been created under the old definition and then remain accessible after the new definition has been evaluated, the accessors and other functions for the new definition may be incompatible with the old instances.
	www.cs.berkeley.edu /~jaety/cs188/clm/node170.html (808 words)

	21.3. Operations on Streams (Site not responding. Last check: 2007-10-12)
		X3J13 also voted in January 1989 to specify exactly which inquiry functions may be applied to closed streams:
		X3J13 voted in January 1989 (CLOSE-CONSTRUCTED-STREAM) to clarify the effect of closing various kinds of streams.
		For example, if the stream performs output to a file that was newly created when the stream was created, then if possible the file is deleted and any previously existing file is not superseded.
	www.music.mcgill.ca /~ferguson/cltl/clm/node185.html (885 words)

	7.1.1. Reference
		X3J13 voted in January 1989 (CONSTANT-MODIFICATION) to clarify that it is an error to destructively modify any object that appears as a constant in executable code, whether within a
		X3J13 voted in June 1988 (FUNCTION-TYPE) to specify that the result of a
		X3J13 voted in June 1988 (FUNCTION-TYPE) to emphasize that, despite the tightening of the definition of the type
	www.dxarts.washington.edu /docs/cltl/clm/node78.html (1687 words)

Try your search on: Qwika (all wikis)