The Yhc compiler generally produces a binary [http://haskell.cs.yale.edu/haskellwiki/Yhc/RTS/hbc bytecode] file (usually named with ''.hbc'' extension) for each Haskell module compiled. These bytecode files are to be interpreted by [http://haskell.cs.yale.edu/haskellwiki/Yhc/Tutorial#yhi yhi], a command-line bytecode interpreter.

+

The Yhc compiler generally produces a binary [[Yhc/RTS/hbc|bytecode]] file (usually named with ''.hbc'' extension) for each Haskell module compiled. These bytecode files are to be interpreted by [[Yhc/Tutorial#yhi|yhi]], a command-line bytecode interpreter.

−

The compiler is also capable of producing a binary [http://haskell.cs.yale.edu/haskellwiki/Yhc/API/Core core] file (usually named with ''.ycr'' extension), and also its human-readable representation for each Haskell module compiled. The internal structure of core is based on significantly simplified NHC98's PosLambda constructs (Yhc is derived from HNC98 code). Core consists of definitions for compiled Haskell functions and data objects.

+

The compiler is also capable of producing a binary [[Yhc/API/Core|core]] file (usually named with ''.ycr'' extension), and also its human-readable representation for each Haskell module compiled. The internal structure of core is based on significantly simplified nhc98's PosLambda constructs (Yhc is derived from nhc98 code). Core consists of definitions for compiled Haskell functions and data objects.

The feature of core linking was added recently to Yhc. This allows for merging core files from several modules together, removing functions that are not used (similar to static linking performed by a traditional Unix or Windows executable linker). The resulting file (usually named with ''.yca'' extension) has the same format as per-module core files.

The feature of core linking was added recently to Yhc. This allows for merging core files from several modules together, removing functions that are not used (similar to static linking performed by a traditional Unix or Windows executable linker). The resulting file (usually named with ''.yca'' extension) has the same format as per-module core files.

Revision as of 01:06, 7 November 2006

Contents

1 Brief Overview

An experimental sub-project, Yhc Core to Javascript Converter (ycr2js), is aimed to create a tool that generates Javascript out of a binary Yhc core file.

The project was started as an experimental patch to nhc98 in attempt to convert its internal PosLambda constructs into Javascript expressions. After some initial success, the project was switched to use the Yhc Core as the source for transformation. Recently, with a great amount of help from the Yhc Team, the project has been integrated into the main Yhc source tree and is moving towards closer integration with the compiler.

Ability to convert an arbitrary Haskell source into Javascript makes it possible to execute Haskell programs in a Web browser. This, in turn, allows for development of both client and server sides of an Internet application entirely in Haskell.

Server side solutions in Haskell have been around for a while, such as HAppS -- Haskell Application Server, Haskell Server Pages, and others. For the client side, HSPClientSide has been recently introduced, which is a close analog to ycr2js. HSPClientSide provides a domain-specific language to define the client side Web page structure (static HTML and Javascript). On the contrary, ycr2js helps convert any compilable Haskell source into Javascript.

2 Principles of Operation

The Yhc compiler generally produces a binary bytecode file (usually named with .hbc extension) for each Haskell module compiled. These bytecode files are to be interpreted by yhi, a command-line bytecode interpreter.

The compiler is also capable of producing a binary core file (usually named with .ycr extension), and also its human-readable representation for each Haskell module compiled. The internal structure of core is based on significantly simplified nhc98's PosLambda constructs (Yhc is derived from nhc98 code). Core consists of definitions for compiled Haskell functions and data objects.

The feature of core linking was added recently to Yhc. This allows for merging core files from several modules together, removing functions that are not used (similar to static linking performed by a traditional Unix or Windows executable linker). The resulting file (usually named with .yca extension) has the same format as per-module core files.

Binary core files may be read back into computer memory using the Yhc Core API functions.

The ycr2js program reads the binary core file specified (.yca or .ycr), and performs conversion of Haskell functions compiled into Core to their Javascript representation storing the generated Javascript code in a file. Resulting Javascript may be embedded on a (X)HTML page to be loaded into a Web browser.