-
Notifications
You must be signed in to change notification settings - Fork 8
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #618 from AmpersandTarski/development
Release 3.8.1
- Loading branch information
Showing
92 changed files
with
1,906 additions
and
2,855 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
CONTEXT RAP IN ENGLISH | ||
|
||
|
||
|
||
PATTERN Modules | ||
CONCEPT Module "A module is a file that contains Ampersand source code." | ||
RELATION filename[Module*FileName] [UNI] | ||
MEANING "Every pattern that is stored in a file system has a FileName." | ||
RELATION filepath[Module*FilePath] [UNI] | ||
MEANING "Every pattern that is stored in a file system has a FilePath." | ||
RELATION includes[Module*Module] | ||
MEANING "Pattern A instantiates B means that all definitions from B are copied into A." | ||
PURPOSE RELATION filename[Module*FileName] | ||
{+ Patterns can be stored in a file system. | ||
To identify a pattern as a file, it has a file name. | ||
The file name follows the conventions of the file system in which the pattern resides. | ||
+} | ||
PURPOSE RELATION filepath[Pattern*FilePath] | ||
{+ For working with file systems that support a folder hierarchy, | ||
patterns can have a file path. | ||
The file path follows the conventions of the file system in which the pattern resides. | ||
+} | ||
ENDCONTEXT |
Oops, something went wrong.