compilar en modula-2 con mocka

Dudas y comentarios sobre otros lenguajes de programación. Si algún lenguaje recibe suficientes preguntas le añadimos nueva categoría.
Responder
Mensaje
Autor
Pantalàimon_
Mensajes: 1345
Registrado: 17/07/2007 2:38 am

compilar en modula-2 con mocka

#1 Mensaje por Pantalàimon_ » 21/09/2009 1:50 pm

Buenas!

Quizá es que he leído muy pocas manpages pero estoy intentando compilar un archivo hellow world en modula-2 y no lo consigo. A ver si entendéis cuál es la manera de compilar con mocka.

Aqui va el man del compilador:

Código: Seleccionar todo

NAME
       mocka - MOCKA, Modula-2 Compiler Karlsruhe running on Linux

SYNOPSIS
       mocka [-s module | -c module | -p module]

       [-d  dir] ...  [-index] [-noindex] [-range] [-norange] [-static] [-nostatic] [-elf] [-noelf] [-g] [-nog] [-gc]  [-nogc] [-ge] [-noge] [-S] [-noS]

       [-D  directory] [-link script] [-edit  script] [-list script] [-asm script] [-syslib dir]



DESCRIPTION
       mocka is used to compile and link programs written in Modula-2.

       mocka -s module translates the DEFINITION MODULE module into a symbol file. This must be present when the IMPLEMENTATION MODULE module or a file importing module is compiled.

       mocka -c module translates the [IMPLEMENTATION] MODULE module into a code file. This  must be present when a program containing module is created.

       mocka -p module creates an executable program for MODULE module.

       If none of the options -s , -c , -p is specified, mocka enters session mode.

       In this mode the user need not worry about consistent module configurations and correct compilation order. Required compilations are triggered automatically. They are based on a dependency graph which is derived from the sources and updated when necessary.

       Session mode also simplifies the correction of errors. If an error is detected a listing is created and the editor is invoked automatically. Errors may be corrected in the listing. After leaving the editor the listing (without the error messages) is written back to the source file.


DEBIAN INSTALLATION
       The original name for the mocka compiler is mc. In  Debian, there is already  a  program by this name, so it has been renamed to mocka. See more documentation in the directory /usr/share/doc/mocka.


OPTIONS
       -s module           Create symbol file for module, i.e. compile the DEFINITION MODULE module in file module.md .

       -c module           Create code file for module, i.e. compile the [IMPLEMENTATION] MODULE module in file module.mi .

       -p module           Create program module, i.e. link code files for MODULE module and all (transitively) imported  modules.

       -d dir              Allow import from modules in library dir. This options may be repeated. Libraries (directories containing compiled modules) are inspected in the order specified. Finally the system library is inspected.

       -index (-noindex)   Generate (don't generate) code for index checks.

       -range (-norange)   Generate (don't generate) code for range checks.

       -static (-nostatic) Link (not) static.

       -elf (-noelf)       Produce assembler code needed for the ELF binary format. The -elf option is passed to the asm and link script.

       -g (-nog)           Produce (no) debugging information using the stabs format. gdb can work with this debugging information. Please read the file README-MOCKA-DEBUGGING in the doc directory of mocka.

       -gc (-nogc)         Produce (no) constant debugging information. gdb can use it, but dbx does currently not work with this.

       -ge (-noge)         Produce (no) enumeration debugging information. Use -noge if you have a buggy gdb like gdb-4.15.1.

       -S (-noS)           The generated symbolic machine code is written to file module.s

       The following options may be used to overwrite installation parameters.

       -D directory        Specifies  a  directory where to place the compilation results (the files *.[dmiros]) in. This option defaults to the current directory.

       -link script        Use  script to invoke ld.  When -p module is specified, mocka collects all imported  modules, checks them for consistency, creates a root module and then invokes script module codefiles 

       -edit script        Use script to invoke the editor. When one of the commands d module or i module is given during session mode script sourcefile is called.

       -list script        Use script to invoke the lister. When an error is detectect during session mode script sourcefile errorfile is called.

       -asm script         Use script to invoke the  assembler.  The  compiler produces assembler code, this script has to call the assembler to produce object code.

       -syslib dir         Use dir as system library.

COMMANDS
       d module            Edit DEFINITION MODULE module. (The module in a d or i command may be omitted. Then the module of a previous d or i command is used.)

       i module            Edit [IMPLEMENTATION] MODULE module.

       s module            Create symbol files for module and all (transitively) imported modules if they are missing or obsolete.

       c module            Create code file for module and symbol files  for module and all (transitively) imported modules if they are missing or obsolete.

       p module            Create code file for module and code and symbol files for all (transitively) imported modules if they are missing or obsolete. Create program module if missing or obsolete. (module may be omitted. Then the module of a  previous p command is used.)

       <empty>             The empty command is used to resume processing after editing a file. It is equivalent to the latest s , c or p command.


       -flag               (where  flag stands for index, noindex, range, norange static, nostatic , g , nog , gc , nogc ,  S , noS , elf , noelf ) has the the same meaning as the corresponding mocka argument.

       -info               Shows current settings of compiler options.

       q                   Quit.

       unixcommand         Commands not in the preceeding list are treated  as Unix commands.

SPECIAL
       Procedures  written in other languages may be accessed by Modula-2 procedures. The compiler follows the type mapping and calling conventions of C. External entities must be defined in foreign modules. These are definition modules where the keyword DEFINITION is replaced by FOREIGN. For such a module the compiler does not insist on an implementation module. When linking a program an argument "M.o" for each foreign module M is passed to ld. (Hence, when an implementation of a foreign module uses a further file N.o, there should be an import of a corresponding (empty) foreign module N.)

FILES
       module.md           Source file of DEFINITION MODULE module.

       module.mi           Source file of [IMPLEMENTATION] MODULE module.

       module.d            Symbol  file for DEFINITION MODULE module (used for inter module type checking).

       module.r            Reference file for module (used for linking).

       module.s            Assembler file for module.

       module.o            Code file for module.

       module              Executable program for MODULE module.

SEE ALSO
       Programming in Modula-2 by Niklaus Wirth (Springer-Verlag Berlin,  Heidelberg, New York, Tokyo; 3rd edition 1985)

BUGS
       Only one mocka process can run in the current directory.  Only modules in the current directory are considered to  determine the compilation order during session mode.
Uno de los grandes problemas es que no acabo de entender la synopsis.

He probado cosas como:

Código: Seleccionar todo

mocka -p hola.md
mocka hola.md -p hola
mocka -p hola hola.md
para ver si seguía la lógica del compilador gcc pero que va...

Gracias por la ayuda, me sería muy necesaria.

Un saludo!

Responder

¿Quién está conectado?

Usuarios navegando por este Foro: No hay usuarios registrados visitando el Foro y 2 invitados