Grammars

From HaFrWiki
Revision as of 10:46, 14 November 2012 by Hjmf (talk | contribs) (Created page with "{{TOCright}} The Grammar of a computer language is an essential part of parsing a computer language. The most common way to store a Grammar is to use the '''E'''xtendend '''B'...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
Access-rights violation
The requested action is not allowed by this wiki website.
See the description below for detailed information.

Detailed Access-rights violation
The requested action has been read access for ⧼wikirbac-title-page (history-access)⧽ Grammars.
The webmaster/administrator has restricted access to this information using the Role Based Access Control (RBAC).
An entry of this violation has been created in the Log-file with timestamp 27 January 2023 16:43:46.
Details access limitation.
  • No-Super-UserGroup 4 All Categories.
  • No-Super-UserGroup 4 All Categories.
  • Restriction for all usergroups's (*) found for cat Index.
  • No access credentials found for Access: History



RBAC-Documentation
See the the website documentation (HaFrWikiCommunity Portal) for more information.

Suggested continuation

Return to Main Page.

The Grammar of a computer language is an essential part of parsing a computer language. The most common way to store a Grammar is to use the Extendend Backus Naur Format (EBNF named after John Backus and Peter Naur). The EBNF of most language are available on the internet, but are not complete. To use these grammars for parsing a complete application for translation purposes it is almost often necessary to make additions/changes, because:

  • An absolute grammar does not exist and should not be made.
  • The grammar should fit to the solution it is intended for.
  • Programmers have their own style. So no computer program is written in the same manner.
  • Platform (or other) specific language implementations.

For the translation of a computer language into another at least 2 different EBNF's are necessary. One is used for the parsing process, the other as a template for/definition of the destination language.

See also[edit]

Internal[edit]

  • Parser Links, Collection of all links related to paring.
  • Javacc, Parsing tool written in Java.
  • Software migration, Description of Business Application Modernization (BAM) Software migration.
  • Translators, Automating migration of code or translating code.

[edit]

External[edit]

See also the internal links for a list of all related links.