Lines Matching refs:version
84 the location and perhaps identifies a particular version of the
96 \gramindex{LIB-VERSION} ::= lib-version LIB-ID VERSION-NUMBER
97 \gramindex{VERSION-NUMBER} ::= version-number NUMBER+
108 current version of the library but also to previously-defined
207 \texttt{name} in path \texttt{path} version \texttt{nnn} is accessed via \texttt{path/name/v\_nnn},
208 and the current version via \texttt{path/name/name}),
209 or should the version be appended to the name of the library (which
210 means that library \texttt{name} in path \texttt{path} version \texttt{nnn} is accessed via
211 \texttt{path/name\_v\_nnn}, and the current version
239 orders tags alphabetically. This coincides with the intended lexikographic version
240 ordering only if main version numbers are not greater than 9.} , one for each version
241 (note that one cannot use cvs version numbers, because they are numbered
242 consecutively, while \CASL version numbers are chosen by the user).
247 of individual version via cgi scripts. However, the advantage
253 a different versioning scheme, with the file name and version
254 number added as parameters to the URL, using, say, ?name and ?version.)
257 together with the particular libray version they belong to.
265 require global version numbers for each package of libraries.
275 version 0.9 uses Numbers version 0.7, and therefore (s)he also should use
276 Numbers version 0.7 when importing StructuredDatatypes version 0.9 in order
278 if the Basic Datatypes have global version numbers which are the same
279 for each library, such that StructuredDatatypes version 0.9 uses
280 Numbers version 0.9. Actually, we are following this policy already
284 version numbers, perhaps a package is just a cvs project or folder
287 the cvs tag is set, but also the version numbers used in the CASL
298 %(however, VSE does not have version control).