Skip to main content
  • Home
  • Development
  • Documentation
  • Donate
  • Operational login
  • Browse the archive

swh logo
SoftwareHeritage
Software
Heritage
Archive
Features
  • Search

  • Downloads

  • Save code now

  • Add forge now

  • Help

https://github.com/virtualagc/virtualagc
25 December 2018, 16:55:25 UTC
  • Code
  • Branches (14)
  • Releases (0)
  • Visits
    • Branches
    • Releases
    • HEAD
    • refs/heads/20080615
    • refs/heads/Fictitious-1201
    • refs/heads/block1
    • refs/heads/counters
    • refs/heads/empty
    • refs/heads/gh-pages
    • refs/heads/luminary130
    • refs/heads/master
    • refs/heads/scenarios
    • refs/heads/schematics
    • refs/heads/wiki
    • refs/import/raw
    • refs/tags/20100220
    No releases to show
  • 22dd35c
  • /
  • SyntaxHighlighting.md
Raw File Download
Take a new snapshot of a software origin

If the archived software origin currently browsed is not synchronized with its upstream version (for instance when new commits have been issued), you can explicitly request Software Heritage to take a new snapshot of it.

Use the form below to proceed. Once a request has been submitted and accepted, it will be processed as soon as possible. You can then check its processing state by visiting this dedicated page.
swh spinner

Processing "take a new snapshot" request ...

To reference or cite the objects present in the Software Heritage archive, permalinks based on SoftWare Hash IDentifiers (SWHIDs) must be used.
Select below a type of object currently browsed in order to display its associated SWHID and permalink.

  • content
  • directory
  • revision
  • snapshot
origin badgecontent badge
swh:1:cnt:85d5ae69c4d4e3e32ad185a54a83aeb516289619
origin badgedirectory badge
swh:1:dir:22dd35ca3bdb6355d3f9c5b92c85d524e80082ce
origin badgerevision badge
swh:1:rev:689b58c51d2268e9fc3a5c61aa74c9321891ddea
origin badgesnapshot badge
swh:1:snp:cdcd2bc43331a436e8c659ba93175ef7d7eb339b

This interface enables to generate software citations, provided that the root directory of browsed objects contains a citation.cff or codemeta.json file.
Select below a type of object currently browsed in order to generate citations for them.

  • content
  • directory
  • revision
  • snapshot
Generate software citation in BibTex format (requires biblatex-software package)
Generating citation ...
Generate software citation in BibTex format (requires biblatex-software package)
Generating citation ...
Generate software citation in BibTex format (requires biblatex-software package)
Generating citation ...
Generate software citation in BibTex format (requires biblatex-software package)
Generating citation ...
Tip revision: 689b58c51d2268e9fc3a5c61aa74c9321891ddea authored by Google Code Exporter on 07 April 2015, 19:26:57 UTC
Migrating wiki contents from Google Code
Tip revision: 689b58c
SyntaxHighlighting.md
![http://virtualagc.googlecode.com/svn/trunk/Apollo32.png](http://virtualagc.googlecode.com/svn/trunk/Apollo32.png)
# 1 Syntax Highlighting AGC/AEA Assembly #
In order to enhance the readability of the AGC and AEA assembler code several syntax highlighting options are available for a select set of tools. These syntax highlighting definition files will attempt to highlight comments, assembler instructions and YUL/LEMAP directives differently from normal text to allow easy recognition of the AGC/AEA specifics as well as the YUL/LEMAP assembler directives. If you are familiar with the list of supported editors below then most likely you do not need additional guidance on how to install the highlight definition files (located in the yaSyntax directory) for your preferred tool. However if you need additional help you can access the "EnableSyntaxAGC" document (Open Office format).

## 1.1 Supported Editors ##
The following list of editors is currently supported:
  * [Code::Blocks](http://www.codeblocks.org/)
  * [Eclipse](http://www.eclipse.org/)
  * [Kate](http://kate-editor.org/)
  * [Textpad](http://www.textpad.com/)
  * [Vim](http://www.vim.org/)
  * [Programmer's Notepad](http://www.pnotepad.org/)
  * [jEdit](http://www.jedit.org/)

The syntax files for each of these editors can be found in the SVN source tree in [Contributed/SyntaxHighlight](http://code.google.com/p/virtualagc/source/browse/#svn/trunk/Contributed/SyntaxHighlight) folder.

## 1.2 Syntax Colours ##
The syntax related colours vary from editor to editor and are in many cases based on user or default preferences. However as a general guideline to aid you in reading and to teach AGC or AEA assembler one can distinguish the following code categories that in most cases will have a different colour for each of the supported editors.

  * Comments (e.g. # Some Comment )
  * AGC Instruction Set (e.g. CAF, BZF )
  * YUL Pseudo Codes (BANK, BLOCK, COUNT)
  * AGC Interpreted Instruction Codes (e.g. STORE, STCALL, COS)
  * Symbols and Labels

Not only are the Interpreted instructions in a different colour they are also enclosed in a combination (assuming no jumps are made out of the code block) of TC INTERPRET and EXIT.

## 1.3 Beyond Editors ##
Besides the syntax highlighting in editors you can also see full browsable code listings on the VirtualAGC project site using the syntax colour scheme (e.g. [FRESH\_START\_AND\_RESTART.agc](http://www.ibiblio.org/apollo/listings/Luminary099/FRESH_START_AND_RESTART.agc.html)) as well as in the SVN source browser of GoogleCode using the google-code-prettify engine (e.g. [FRESH\_START\_AND\_RESTART.agc](http://code.google.com/p/virtualagc/source/browse/trunk/Luminary099/FRESH_START_AND_RESTART.agc)).

back to top

Software Heritage — Copyright (C) 2015–2025, The Software Heritage developers. License: GNU AGPLv3+.
The source code of Software Heritage itself is available on our development forge.
The source code files archived by Software Heritage are available under their own copyright and licenses.
Terms of use: Archive access, API— Content policy— Contact— JavaScript license information— Web API