4tH compiler 3.5c (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News 4tH compiler 3.5c (Default branch)
# 1  
Old 12-24-2007
4tH compiler 3.5c (Default branch)

Image4tH is a Forth compiler with a little difference.Instead of the standard Forth engine it features aconventional compiler. 4tH is a very smallcompiler that can create bytecode, C-embeddablebytecode, standalone executables, but also worksfine as a scripting language. It supports about 95%of the ANS Forth CORE wordset and featuresconditional compilation, pipes, files, assertions,forward declarations, enumerations, structures,suspended execution, recursion, include files,etc. It comes with an RPN calculator, line editor,compiler, decompiler, C-source generator, a virtual machine, and a multitasking environment.License: GNU Lesser General Public License (LGPL)Changes:
The words C and OFFSET have been added. The multitasking environment has been fully integrated in the source tree.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
JOCAMLDEP(1)						      General Commands Manual						      JOCAMLDEP(1)

NAME
jocamldep - Dependency generator for JoCaml SYNOPSIS
jocamldep [ -I lib-dir ] filename ... DESCRIPTION
The jocamldep(1) command scans a set of Objective Caml source files (.ml and .mli files) for references to external compilation units, and outputs dependency lines in a format suitable for the make(1) utility. This ensures that make will compile the source files in the correct order, and recompile those files that need to when a source file is modified. The typical usage is: jocamldep options *.mli *.ml > .depend where .depend is the file that should contain the dependencies. Dependencies are generated both for compiling with the bytecode compiler jocamlc(1) and with the native-code compiler jocamlopt(1). OPTIONS
The following command-line option is recognized by jocamldep(1). -I directory Add the given directory to the list of directories searched for source files. If a source file foo.ml mentions an external compila- tion unit Bar, a dependency on that unit's interface bar.cmi is generated only if the source for bar is found in the current direc- tory or in one of the directories specified with -I. Otherwise, Bar is assumed to be a module form the standard library, and no dependencies are generated. For programs that span multiple directories, it is recommended to pass jocamldep(1) the same -I options that are passed to the compiler. -native Generate dependencies for a pure native-code program (no bytecode version). When an implementation file (.ml file) has no explicit interface file (.mli file), jocamldep(1) generates dependencies on the bytecode compiled file (.cmo file) to reflect interface changes. This can cause unnecessary bytecode recompilations for programs that are compiled to native-code only. The flag -native causes dependencies on native compiled files (.cmx) to be generated instead of on .cmo files. (This flag makes no difference if all source files have explicit .mli interface files.) SEE ALSO
jocamlc(1), jocamlopt(1). The Objective Caml user's manual, chapter "Dependency generator". JOCAMLDEP(1)