PHFC project is a CUSP emulator written to be as ANSI C compliant as possible.
PHFC stands for any of the following:
· Phaethon's Hack For CUSP
· PHFC Hobbles Functional Chips
· PHFC Has Funny Characteristics
· PHFC Handles CUSP
Some may tell you that "PHFC" is nothing more than the result of applying
ROT-13 to "CUSP", and that the names were backronymed. That's all vicious lies, don't believe them.
CUSP Background
CUSP stands for "Carleton's Utterly Simple Processor". It is a fictional
microprocessor developed at the Department of Systems and Computer Engineering of the University of Carleton (somewhere in Canada), along with a corresponding textbook, to assist in the instruction of the machine language course.
The original CUSP emulator was written in Turbo Pascal, and compiled for the MS-DOS platform. It uses a (relatively) cheesy text-character GUI during use. Since it's initial release, the original CUSP emulator was released in binary-only form (no source code). Also, it has never been updated to use more modern graphical systems. The most recent version I can find is labled "CUSP Version 5.00", copyrighted in 1991 by John C. Bryant and Gerald M. Karam.
Goals of PHFC
· The original CUSP emulator was written in Turbo Pascal. PHFC is to be written mostly in C.
· The original CUSP was released under a presumable non-free license.
PHFC is covered by the GNU GPL.
· The core of PHFC, the main CUSP emulator, is to be maintained in pure ANSI C. This is to make the emulator core far more portable than the original CUSP.
· There is a part of PHFC that need not be in ANSI C, much less any kind of C. This is the platform-dependant code; the user interface to the PHFC core.
· The core emulator is to remain portable. The interface, though, doesn't need to be portable, to exploit the host's full range of interfacing (graphics).
· And most of all, to get UCLA to ditch CUSP for their Computer Science's
Assembly Language course.
Product's homepage