I've been writing code since 1982(?) (when did the Apple II+ come out??). I've written in BASIC, Assembly, Pascal, C, Verilog, Perl, php, javascript, csh, awk/sed.....

Programs and scripts

These are provided for active use, and may still be under continuing development. Some are large, some are simple, but hey why recreate the wheel if you don't have to? (code offered in that spirit)

RosterTool

RosterTool is a fairly involved (~4000 lines of code) Perl/mySQL script for club/organization membership maintenance. See the RosterTool web site for a full demo and source code.

DVDcover

DVDcover is a simple Perl script (requires ImageMagick) that will crank out quick DVD covers (text-only) for DVR/PVR/Tivo archives.

Tissue (dive simulation tool)

Tissue is a scuba simulation (in C) for gas absorption into tissues, based upon the Haldanean theory. Replicates the US Navy, and PADI RDP dive tables. (note program will not compile as distributed, see inline comment for end-user warning and how to correct. Offered for educational purposes only.)

Research references, etc contained in code comments.

BridgeScore

(in early development) BridgeScore, my first real attempt at OO. Written in C# for the Pocket PC. Track bidding, final contracts, and opening leads for a game of Duplicate Bridge. After entering final results, will generate post-mortem stats of how you did as declarer, and how you did on defense.

It will be of most use for games where hand-records are available, showing the cards for each hand that was played. With the recorded bidding, and hand records, you can easily review what you did well, and what you hope to do better next time, as well as discuss bidding dilemnas.

The main idea is to automate the hardcopy scoresheet I developed and distribute on my cards page.

Web scripts

A few random web scripts that may be useful.

• fdl.cgi File Download, Perl cgi script to do file download from a non-disclosed directory. Must be a local link or will not serve file.
• image.cgi serves an image from non-disclosed directory. Must be called locally. Provides reasonable security for images, and should prevent any deep linking to you.

Other code samples

And a collection of samples from other things I've done.

• Perl, pins.pl, a Perl script to generate FPGA constraint files (for Synplify, Xilinx) from Cadence PBA schematics.
• C, this is one file (out of several) needed for what was essentially a 2-pass compiler that I wrote. It took a data-file (sample) as its input that was formatted according to the language I designed. This datafile defined registers for FPGAs/ASICs, allowing for bit-by-bit descriptions, block definitions of registers (ie. create 16 registers with this same definition, name them RegX with X going from 2..17) and would spit out multiple output files, including;
  • Test firmware in C (produced 100s to 1000s of lines of C test code for chip bring-up/test) sample
  • Verilog test code (again, 100s to 1000s of lines of Verilog code for use in simulation)
  • Interleaf documentation (the Word processing tool we used). Produced a table with all register and bit definitions. sample
  • Several other minor output formats.
  For an average chip, this would produce several 1000 lines of code, and 30+ pages of documentation, saving several man-weeks of development time.
• Verilog Code from what would have been a 1M+ gate Xilinx, with blocks running to 86mHz.