Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
curry-frontend
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
62
Issues
62
List
Boards
Labels
Service Desk
Milestones
Merge Requests
3
Merge Requests
3
Operations
Operations
Incidents
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
curry
curry-frontend
Commits
6d0080c2
Commit
6d0080c2
authored
Apr 06, 2020
by
Fredrik Wieczerkowski
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update project description
parent
b20d10c4
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
6 additions
and
10 deletions
+6
-10
README.md
README.md
+6
-10
No files found.
README.md
View file @
6d0080c2
# Münster-Curry-Compiler
Distribution zur Anwendung als Frontend in PAKCS
# Curry Frontend
The Curry frontend parses source files (
`.curry`
), emits errors and
warnings, performs various checks and transformations and
generates FlatCurry (
`.fcy`
,
`.fint`
) or AbstractCurry (
`.acy`
,
`.uacy`
).
Letztes Update: 27.10.05
Diese Distribution enthält die modifizierte Version des
Münster-Curry-Compilers (MCC) für die Verwendung als Frontend in PAKCS. Dieses
System ist u.a. in der Lage aus Curry-Programmen (entwickelt nach
PAKCS-Standard) Flat-Darstellungen (FlatCurry ".fcy", FlatInterface ".fint"
und FlatXML "_flat.xml"), sowie Abstract-Darstellungen (AbstractCurry ".acy"
und untyped AbstractCurry ".uacy") zu generieren.
The project originated from a modified version of the
Münster-Curry-Compiler (MCC) for use as a frontend in PAKCS.
## 1 Installation
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment