|
|
Class: PackageId
Object
|
+--PackageId
- Package:
- stx:libbasic
- Category:
- System-Support-Projects
- Version:
- rev:
1.16
date: 2009/10/22 15:43:27
- user: cg
- file: PackageId.st directory: libbasic
- module: stx stc-classLibrary: libbasic
Represents packageID's.
Knows the relationship between modules and directories in the package-organization.
defaults
-
noProjectID
-
return the symbol used to tag classes and methods which are loose.
This means: not yet assigned to a particular project.
instance creation
-
from: aStringOrSymbol
-
-
module: moduleString directory: directoryString
-
accessing
-
module: moduleString directory: directoryString
-
-
packageIdString: something
-
-
string
-
comparing
-
= aPackageId
-
compares equal to a corresponding string
-
hash
-
converting
-
asPackageId
-
-
asString
-
-
asSymbol
-
printing
-
printOn: aStream
-
queries
-
directory
-
return the directory component. Thats the rest after the colon.
The module is typically used to define the project-path or project-id within its
sourcecode repository (which is selected via the module).
-
isModuleId
-
true if this is a module-id only (i.e. no directory component present).
These are not allowed to be used as real projects, but only for organization.
The reason is that this is used as selector to select the sourceCodeManager and
also the managers repository
-
libraryName
-
return the name of the library, when compiled to a binary (i.e. dll/so).
To avoid conflicts with the projectDefinition class
(which is named <module>_<directory_components>), we prefix the library name
with 'lib'. This has the added advantage, that under unix, linking can be done with
'-l'shortName.
-
module
-
return the module component. Thats the first component up to the colon.
The module is typically used to select a corresponding sourcecode repository.
-
parentPackage
-
-
pathRelativeToTopDirectory
-
-
pathRelativeToTopDirectory: aDirectory
-
-
projectDefinitionClass
-
|