Generic Function | Package: ide | ToC | DocOverview | CGDoc | RelNotes | FAQ | Index | PermutedIndex
| Allegro CL version 10.1 Unrevised from 10.0 to 10.1. 10.0 version

## project-package-name

Arguments: project

The default method for this generic function returns a keyword symbol naming the default package that is used for source code that is auto-generated for the forms of a project. This package is used for all forms whose form-package-name is `nil`, as it is by default; in other words, it is used for all forms that do not explicitly override this project-wide default. The value of this property for the current project is displayed on the Options tab of the Project Manager dialog. The setf of this function may be called to change the default package of the project.

When creating a new project, we strongly recommend that you decide on a package name for the project and specify it in the Project Manager before creating forms or source code for the project (unless you're content with using the default cg-user package). When changing the package later, it can be tedious to find all of the places where you may need to update package references in the project's source code, including the .bil files that are generated automatically for forms.

When running the complete application, either by using the Run | Run Project command or by using the File | Build Project Distribution command, the variable `*package*` will initially be set to the project's default package. This is not done by the Run | Run Form command, though, because no new process is created for a running form.

The package must exist before setf'ing this value. The package is created automatically if needed when you enter a project package name on the Options tab of the Project Manager dialog. The next File | Save All command will then save the .lpr project definition file to contain a minimal defpackage form for the package to allow the .lpr file to load without error and to allow all of the project's source code files to be "in" the project's package, including any project file where you may have specified a more complete defpackage form.

See form-package-name for details on when and how the package is used. See also project-package.

Copyright (c) 1998-2022, Franz Inc. Lafayette, CA., USA. All rights reserved.
This page was not revised from the 10.0 page.
Created 2019.8.20.

|  | ToC | DocOverview | CGDoc | RelNotes | FAQ | Index | PermutedIndex
| Allegro CL version 10.1 Unrevised from 10.0 to 10.1. 10.0 version