Do you have a Clipper programming question that you're thinking of asking me? Before you do please ensure that you've exhausted all other resources.

clFFFN - clFindFirst()/clFindNext() functions contains three functions that provide an alternative to using Clipper's DIRECTORY() function. I put this archive together after a comp.lang.clipper discussion about the array size limit in CA-Clipper and how this affects how many files you can process using DIRECTORY().

csyScan - Class(y) class scanner

csyScan is a simple Python script for scanning a set of Clipper sources and producing a simple tree to show the class hierarchy. The method used isn't very clever, the output isn't very pretty, but it does the job. I tend to use it to produce quick and dirty documentation.

Obviously, to use the script, you'll need a copy of Python, you will find DOS and Windows versions of Python on the Python homepage.

A word of warning. I've not made any attempt to support multiple inheritance.

csyScan can also produce simple Norton Guide source that includes the actual class definition code behind each class name in the list. See for an example of how to turn this on.

If you want to scan Xbase++ code, you can also use For it to work, you will also need

DGScan - DGROUP Usage Scanner For Clipper

DGScan is a handy utility for Clipper programmers who are worried about DGROUP usage in their own code and in other people's code. Using DGScan you can scan OBJ and LIB files and find possible DGROUP usage.

IsFormat - Quick and dirty string format checker contains the source and an object file for a CA-Clipper function that quickly checks the content of a string against a format. The format itself is very basic when compared with CA-Clipper's format abilities but the idea behind this code is to be quick and dirty.

A function like this might be handy for checking things like postal codes.

MVList - Get a list of Clipper MemVars at runtime

In you'll find some code that should help those who want to get a list of Clipper MEMVARs, from code, at runtime. This question crops up from time to time in comp.lang.clipper and so I offer this code as a possible solution.

OSLib - OS Checking Library

OSLib is a small and simple library that gives the Clipper programmer a small number of functions for checking what kind of environment their application is running in. It can check for MS-Windows, NT and OS/2 and it also contains functions for releasing time slices back to the host OS.

The functions in this library can be found in other libs too, but OSLib was written at the request of a couple of people in comp.lang.clipper. OSLib is not supposed to replace anything or be better than anything, but it's a small library that people can be pointed to when they ask how they can detect MS-Windows or OS/2 for example.

If you want to see what OSLib contains then take a look at its Norton Guide. The archive itself is downloadable from here in ZIP format. When you extract this ZIP file make sure you tell your unpacker to create all stored directories.

Page last modified: 2017-07-04 11:09:27 UT
Dave Pearson <>
Valid XHTML 1.1 Valid CSS