YNREADER() Short: ------ YNREADER() Creates specialized Yes/No get reader block Returns: -------- <bReader> => get reader block for logical GET Syntax: ------- YNREADER() Description: ------------ Creates a reader block that pops up a Yes/No window to get the logical value for the current get. Implement by using the SEND keyword for your @Say..Get.. statements. i.e. @10,10 say blah get blahblah SEND reader:=YNREADER() Use this on a LOGICAL get only. Examples: --------- // while in the get V1, a Yes/No window pops up for logical selection v1 := .f. @10,10 get v1 send reader := ynreader() READ Source: ------- S_READRS.PRG
Tag Archives: Logical
SP_GENVAL
GENVAL()
Short:
------
GENVAL() Generic VALID clause validation with message
Returns:
--------
<lValid> => logical result of passed condition
Syntax:
-------
GENVAL(expValid,expMessage)
Description:
------------
Evaluates <expValid>, which is either a bode block or
a string to be macro expanded, as a logical value. If result is
False, displays message <expMessage> and waits for a keypress.
<expMessage> can be a single string, or an array of strings (see
aMsg() ).
Examples:
---------
if genval("fcount() < 60",'Too many fields')
COPY TO TEMP
endif
* ...or as a VALID CLAUSE macro'd
@10,10 get lname VALID ;
GENVAL("!empty(lname)","Need a last name")
* ...or as a VALID CLAUSE eval'd
@10,10 get fname VALID ;
GENVAL( { || !empty(fname) },"Need a last name")
Source:
-------
S_GENVA.PRG
SP_BLANKFIELD
BLANKFIELD()
Short:
------
BLANKFIELD() Returns a blank value corresponding to a field
Returns:
--------
<expBlank> => blank value, corresponding to a field
Syntax:
-------
BLANKFIELD(cField)
Description:
------------
<cField> is the name of the field. Can also include
the alias
A blank value is returned:
For: Character Spaces the length of the field
Numeric Zero
Logical .f.
Date Blank date
Memo ""
Examples:
---------
// fill an array with matching blanks for the record - good
// for an ADD routine
aAdds := array(fcount())
for i = 1 to fcount()
aAdds[i] := BLANKFIELD(field(i))
next
Source:
-------
S_BLANKS.PRG
Coding Guidelines
Coding Guidelines
( by Greg Holmes )
| Language Syntax The general rule of thumb is: built-in features in lowercase, and custom-written functions in mixed case. When specifying the complete syntax of a language element in documentation, the input items, parameters, and so on are referred to using the following symbols:
For example:
Metasymbols provide a place holder for syntax elements, and they describe the expected data types. A metasymbol consists of one or more lowercase data type designators followed by a mixed case description. This is known as Hungarian Notation.
In this example,
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
Filenames and Aliases All filenames, in any context, are in upper case. Filenames follow DOS naming conventions (preferably limited to letters, numbers, and the underscore).
When referring to specific file types in documentation, include the period. |
|
Fieldnames Fieldnames are all uppercase, and always include the alias of the table. Fieldnames may contain underscores, but should not begin with one (because the underscore is generally used to indicate an internal symbol).
|
|
Memory Variables Memory variables consist of a lowercase type designator followed by a mixed case description (see Hungarian Notation). Although CA-Clipper only recognizes the first 10 characters as unique, variable names may be longer.
If you use Hungarian Notation for your memory variable names and include the table alias with fieldnames, there will be no conflict between the two. |
|
Commands, Functions, and Keywords All built-in commands, functions, and keywords are lowercase. In documentation, the font should be Courier or a similar font. If fonts are not available, then bold or CAPITALIZE the word for emphasis. Never use abbreviations — this practice is not necessary with a compiler, although it was common in the early days of dBase (which was an interpreter). There should never be a space between the function name and the opening parenthesis. Also, note that the iif() function should never be spelled if().
When specifying commands that have clauses in documentation, separate the keywords with an ellipsis (
|
|
Programmer-Defined Functions & Procedures These begin with an uppercase letter, followed by mixed case letters as appropriate.
Function and procedure names may contain underscores, but should not begin with one (they may conflict with internal functions which often start with an underscore). There should be only one
The return value of a function is not enclosed in parentheses, although parentheses may be used to clarify a complex expression.
|
|
Preprocessor Directives Preprocessor directives are lowercase and are preceded by the # sign.
Optionally, you may use single quotes around header files that come with CA-Clipper and double quotes around your own. This convention is purely voluntary, but it helps to distinguish between the two. For example:
Manifest constants are uppercase.
Pseudo-function names should also be uppercase.
|
|
Declarations Local variables are grouped according to functionality, and may be declared on one or more lines. The declarations appear as the first code at the beginning of a function or procedure.
Variables may be declared one per line and accompanied by a description.
The description can be omitted if better variable names are chosen.
Variables can be initialized when they are declared, although it is often clearer (and safer) to initialize them immediately before they are used.
|
|
Logicals The .T. and .F. are typed in uppercase. |
|
Operators The in-line assignment operator ( :=) is used for all assignments, and the exact comparison operator (==) is used for all comparisons.
Although the compound assignment operators (
The increment (
|
|
Spacing Whenever a list of two or more items is separated by commas, the commas are followed by a space.
Spaces may be used between successive parentheses.
Spaces should surround all operators for readability.
In declarations, often spaces are not used around the assignment operator. This tends to make searching for the declaration of a variable easier.
Thus, searching for “ |
|
Indentation Indenting control structures is one of the easiest techniques, yet it improves the readability the most. Indent control structures and the code within functions and procedures 3 spaces.
Case statements in a do…case structure are also indented 3 spaces.
|
|
Tabs Do not use tabs in source code — insert spaces instead. Tabs cause problems when printing or when moving from one editor to another, because of the lack of a standard tab width between editors and printers. Typically, printers expand tabs to 8 spaces which easily causes nested control structures to fall off the right-hand side of the page. Commonly, a source code editing program will insert the appropriate number of spaces when the <TAB> key is hit. |
|
Line Continuation When a line of code approaches the 80th column, interrupt the code at an appropriate spot with a semicolon and continue on the next line. Indent the line so that it lines up in a readable manner.
To continue a character string, end the first line with a quote and a plus sign and place the remainder on the next line. Try to choose a logical place in the string to break it, either at a punctuation mark or after a space.
|
|
Quotes Use double quotes for text that needs to be translated (will appear on the screen), and single quotes for other strings.
This is a simple but extremely effective technique because translation departments often want to see the messages in context (in the source code), so the different quote types indicate which messages are to be translated and which should be left alone. |
|
Comments Comments are structured just like English sentences, with a capital letter at the beginning and a period at the end.
You may encounter old-style comment indicators if you maintain older (Summer’87 and earlier) code.
For in-line comments, use the double slashes.
Note that the ‘ |
FT_XTOY
FT_XTOY()
Convert from any data type to any other data type
Syntax
FT_XTOY( <xValueToConvert>, <cTypeToConvertTo> ;
[, <lWantYesNo> ] ) -> xResult
Arguments
<xValueToConvert> is the value to convert.
<cTypeToConvertTo> is the type of value to convert to
("C","D","L","N","A" or "B").
<lWantYesNo> is a logical to signal if 'Y' or 'N' is to be returned
if Converting a logical, otherwise '.T.' or '.F.' will be returned
for logicals.
Returns
The original value converted to the new type.
Description
This function converts a value of character, date, numeric, logical,
array or code block type to any of the other type. While it is
guaranteed to return a value of the correct type, that value may not
be meaningful (i.e., converting from a code block returns an EMPTY()
value of the desired type).
Examples
nNumericValue := FT_XTOY(cInputValue, "N")
IF (FT_XTOY(nInputValue, "L"))
Source: ANY2ANY.PRG
Author: David Husnian
FT Toolkit Overview
NANFOR.LIB Working Group G. Scott [71620,1521]
Overview UCLA
Version 2.1 October, 1992
THE NANFORUM TOOLKIT (NANFOR.LIB)
PUBLIC DOMAIN USER SUPPORTED CLIPPER FUNCTION LIBRARY
.
1 INTRODUCTION
This is a standard for establishing and maintaining NANFOR.LIB, a public-domain, user-supported library of functions designed to interface with Computer Associates CA-Clipper, version 5.01a, and later. You are encouraged to read it over and forward comments to Glenn Scott, CIS ID [71620,1521].
1.1 History
In October and November of 1990, a discussion on the evolution of third-party products, vendors, and marketing took place on the CompuServe Information Service’s Nantucket Forum (NANFORUM). During this discussion, a forum subscriber named Alexander Santic suggested the idea of a user-supported Clipper function library, available to all on the CompuServe Information Service (CIS). A number of subscribers, including several Clipper third party developers, and some Nantucket employees, expressed their support. This standard was a first step toward organizing such an endeavor.
Release 1.0 of the toolkit was made available in April, 1991 and had nearly 150 functions. By the time version 2.0 was released in August, 1991, the 1.0 library had been downloaded nearly 700 times by CompuServe users. By October of 1992, release 2.0 had been downloaded over 2100 times. The source code had been downloaded nearly 1500 times. In addition, release 2.0 was placed on the massive Internet archive site called SIMTEL20 where it was downloaded by CA- Clipper users worldwide. Over the course of the year that release 2.0 was available, seven patches were issued, each one gathering nearly 1000 downloads.
Computer Associates International, Inc. acquired Nantucket in the summer of 1992 and subsequently renamed NANFORUM to simply CLIPPER. In addition, the Clipper product itself was renamed to CA-CLIPPER. Despite the name changes, forum members decided to keep the toolkit’s name as “The Nanforum Toolkit,” partly for nostalgia. References to NANFORUM in this RFC have been replaced with CLIPPER.
1.2 Trademarks
CA-Clipper is a registered trademark of Computer Associates International, Inc. Computer Associates will be referred to as CA throughout this document.
1.3 Relationship to CA and third party
NANFOR.LIB is a project independent of any third party developer or CA. There is no official “sanction” or “seal of approval” from CA of any kind. In addition, NANFOR.LIB routines will be accepted and included without regard for whether or not routines performing a similar function are included in a commercial third party or CA product.
It is desired that NANFOR.LIB not compete with third party products but rather fill in the holes in CA-Clipper’s standard library. However, there will be some overlap into commercial third-party library functions, so it would be best if this is never taken into consideration when deciding on including a particular function.
Developers submitting NANFOR.LIB routines can and will be corporate developers, third party developers, independent consultant / programmers, hobbyists, and other CA-Clipper people. Perhaps even CA employees will contribute. No one is excluded or included due to any particular affiliation.
CA employees submitting functions are doing so as individuals, and are not making a policy of involving CA in the project, nor are they committing CA to supporting the public domain library.
1.4 CA-Clipper version supported
NANFOR.LIB functions, no matter what language they are written in, will be designed to work with CA-Clipper version 5.01a and later. Many of the functions, particularly those that use the EXTEND system, will be compatible with the Summer 1987 version of CA-Clipper. However, ensuring Summer 87 compatibility will be the responsibility of the user. If a user wants a function to work with Summer 87, she will have to modify the code herself if necessary. In many cases, this is a trivial task.
1.5 Queries from new users
Queries from new users interested in finding NANFOR.LIB should be handled in a uniform and courteous way. A short text file will be created that will briefly explain NANFOR.LIB, who the current people maintaining it are, and how to get a hold of it. This text message can be sent in response to any query. TAPCIS users will find this method very easy to implement.
2 DISTRIBUTION
2.1 Public Domain
NANFOR.LIB, its source code, and documentation will be public-domain software. It is not for “sale”, and shall not be sold. No fee or contribution of any kind will be required for anyone wanting a copy, other than what they would normally pay to download it from CompuServe. Users will be encouraged to submit functions via CompuServe.
2.2 Official repository
It is possible that copies of NANFOR.LIB will be downloaded and distributed elsewhere. This is encouraged, but the only copy of NANFOR.LIB and all associated documentation that will be maintained by volunteers is in an appropriate library on the CIS CLIPPER Forum.
2.2.1 Contents
The deliverables that make up the official posting on CompuServe shall be:
2.2.1.1 NFLIB.ZIP
This will contain the files NANFOR.LIB (library), and NANFOR.NG (Norton Guide).
2.2.1.2 NFSRC.ZIP
This will contain all the library source code, makefile, and other source-code related materials.
2.2.1.3 NFINQ.TXT
This is a short text file used as a response to new user queries (see paragraph 1.5)
2.2.1.4 NFRFC.ZIP
This contains an ASCII format, as well as a WordPerfect 5.1 format copy of NANFOR.RFC named NFRFC.TXT (ASCII) and NFRFC.WP5 (WordPerfect 5.1).
2.2.1.5 NFHDRS.ZIP
This contains templates of the file and documentation header blocks, including a sample, for prospective authors (FTHDR.PRG, FTHDR.ASM, FTHDR.SAM)
2.2.1.6 PATx.ZIP
These are patch files (see paragraph 4.5.1).
3 POLICY ON INCLUDING FUNCTIONS
3.1 “Best Function”
It is possible that more than one developer will submit a function or package of functions that perform substantially the same services. In that event, the referees will choose one to be included based on power, functionality, flexibility, and ease of use. Due to the cooperative, non-commercial nature of the library, no one’s feelings should be hurt by excluding duplicate functions.
In addition, it is possible that two substantially similar functions or packages will benefit from merging them together to provide new functionality. This will be the prerogative of the referees (see paragraph 6.3), in close consultation with the authors.
3.2 Public Domain
Each author submitting source code must include as part of that code a statement that this is an original work and that he or she is placing the code into the public domain. The librarian (see paragraph 6.1) and referees should make a reasonable effort to be sure no copyrighted source code, such as that supplied with some third party libraries, makes it into NANFOR.LIB. However, under no circumstances will the librarian, referees, or any other party other than the submitter be responsible for copyrighted code making it into the library accidentally.
3.3 Source code
Full source code must be provided by the author for every routine to be included in NANFOR.LIB. No routine, no matter what language, will be put into the library on the basis of submitted object code.
3.4 Proper submission
Due to the volume of submissions expected, librarians and referees may not have the time to fix inconsistencies in documentation format, function naming, and other requirements. Therefore, the librarian shall expect source code to arrive in proper format before proceeding further with it.
3.5 Quality and perceived usefulness
In a cooperative effort like this, it is very difficult to enforce some standard of quality and/or usefulness. For example, a package of functions to handle the military’s “Zulu time” may be very useful to some, and unnecessary to others.
The Nanforum Toolkit will by its very nature be a hodgepodge of routines, some of very high quality, some not so high. It is up to the users to improve it. It will be complete in some areas and vastly inadequate in others. It is up to the users to fill in the holes.
We shall err on the side of including “questionable” functions, provided they seem to work. Debates on the quality of the library’s source code shall be encouraged and will take place in the proper message section of the CompuServe CLIPPER forum.
4 LIBRARY MAINTENANCE PROCEDURE
4.1 Selection procedure
Source code will be submitted to the librarian, the documenter (see paragraph 6.2), or one of the referees. Code will be added if it has been reviewed, and approved by at least one, but preferably two, referees.
Code not meeting the documentation or source code formatting standards will generally be returned to the author with instructions.
Referees will test the submitted code. When the referees have finished evaluating a submission, they will report their approval or disapproval to the librarian, with comments.
Every effort should be made to make sure that the C and ASM functions are reviewed by referees with suitable C and ASM experience.
4.2 Update interval
As new functions are submitted, they will added to the library, and the documentation updated. Because this is a volunteer project, and because of the complexity involved in coordinating testing, documentation, and delivery, there will be no fixed interval for updates.
4.3 Version control
NANFOR.LIB will use a numeric version number as follows:
The major version will be numeric, starting from 1. This will change with each quarterly update. The minor version will change with each bug fix. This will start with zero and continue until the next major update, at which point it will revert to zero again.
Typical version numbers might be 1.1, 2.12, 15.2, etc.
The .LIB file, and all associated files, will carry a date stamp corresponding to the day it is released on the CLIPPER forum. The file time stamps shall correspond to the version number (i.e., 1:03am is version 1.3).
4.4 Announcing updates
As the library and its associated documentation are updated, simple announcements will be posted on the CLIPPER forum. This is the only place where an update shall be announced. An update will be announced after it has been successfully uploaded to the appropriate library on CompuServe.
4.5 Bug reports and fixes
The librarian will correlate and verify all bug reports, with the help of the referees. If the referees believe a bug to be serious, they will fix it and the librarian will release a maintenance upgrade immediately. If they consider it a minor bug, they will fix it but wait for the next scheduled upgrade to release it. In this case, a bug fix may be released as a “Patch.”
4.5.1 Patches
A “patch” is simply an ASCII text file containing instructions for editing the source code to a misbehaving function or group of functions. Patches may appear in the CIS library before a maintenance release or quarterly upgrade. A patch file will have a name of the form
PATn.ZIP
where <n> is a number starting from 1. Patches will be numbered sequentially. Patches will be deleted every time a new version of NANFOR.LIB goes on-line.
A patch zipfile may optionally contain .OBJ files to be replaced in user libraries via a LIB utility.
4.6 Technical Support
Technical support will work just as any technical subject on the CompuServe CLIPPER forum works. Users will post questions and suggestions to a particular message area or thread, and anyone who knows the answer should respond. No one is obliged to answer, but it is considered good form to respond with something, even if one doesn’t know the answer.
Support will include help on recompiling the routines or modifying the source.
4.7 Linker Compatibility
In order to assist users of CA-Clipper third party linkers (such as WarpLink or Blinker), NANFOR.LIB may need to broken up into root and overlay sections. How this will be done will be determined when splitting becomes necessary.
The librarian is not responsible for testing every possible linker for NANFOR.LIB compatibility. It is hoped that linker users will submit appropriate link scripts or other documentation for posting in the appropriate section on the CLIPPER forum.
4.8 Splitting NANFOR.LIB by functional category
It is possible that at some future date, it will make sense to split NANFOR.LIB into separate functional areas (e.g., video routines vs. date routines, etc). This RFC will be modified accordingly should that need arise.
5 FUNCTION CODING STANDARDS
The goal of this standard is not to force anyone to rewrite his code for this library, but to create some consistency among the functions so that they may more easily maintained and understood by all CA-Clipper developers, both novice and advanced.
However, it is extremely important that anyone submitting code attach the proper headers and documentation and fill them out correctly. This will make it much easier for code to be added to the library.
5.1 Required sections for each function
5.1.1 Header (author name/etc, version ctrl info)
Figure 1 shows a header that must be included at the top of every piece of source code submitted to the library. This header will work with both CA-Clipper and C code. For ASM code, substitute each asterisk (“*”) with a semicolon (“;”) and delete the slashes (“/”).
/* * File......: * Author....: * CIS ID....: x, x * Date......: $Date$ * Revision..: $Revision$ * Log file..: $Logfile$ * * * Modification history: * --------------------- * * $Log$ * */
Figure 1 - Standard function header.
Note that the date, revision, logfile, and modification history fields will be maintained by the librarian and should not be edited or adjusted by code authors.
The “File” field shall contain the source file name. This is often independent of the individual function name. For example, a function named ft_screen() would be included in SCREEN.PRG. As a rule, source files (.PRG, .C, .ASM) should not have the “FT” prefix.
The “Author” field should have the author’s full name, and CIS number. A CIS number is important, as this will make bug fixing and other correspondence easier.
5.1.2 Public domain disclaimer
Authors shall simply state “This is an original work by [Author’s name] and is hereby placed in the public domain.”
5.1.3 Documentation block
/* $DOC$ * $FUNCNAME$ * * $ONELINER$ * * $SYNTAX$ * * $ARGUMENTS$ * * $RETURNS$ * * $DESCRIPTION$ * * $EXAMPLES$ * * $SEEALSO$ * * $INCLUDE$ * * $END$ */
Figure 2 – Standard Documentation Header
The documentation block must be carefully formatted as it is used by the documenter to produce the Norton Guide documentation for the library.
The keywords enclosed in dollar-signs delimit sections of the documentation header analogous to those in the CA-Clipper 5.0 documentation. Documentation should be written in the same style and flavor as the CA material, if possible. Refer to the CA-Clipper documentation for more detail and numerous examples.
The documentation will appear on comment lines between the keywords. Examples are optional. Do not put documentation on the same line as the comment keyword.
Note that the $DOC$ and $END$ keywords serve as delimiters. Do not place any text between $DOC$ and $FUNCNAME$, or any documentation after the $END$ keyword, unless that documentation belongs in the source code file and not in the resultant Norton Guide file.
The $FUNCNAME$ keyword should be followed by the function name, with parentheses, and no arguments or syntax, such as:
$FUNCNAME$ ft_screen()
Note the indent for readability. Parentheses shall be added after the function name as shown above.
The $ONELINER$ keyword should be followed by a simple statement expressing what the function does, phrased in the form of a command, e.g.:
$ONELINER$
Sum the values in an array
The length of the entire $ONELINER$ shall not exceed 60 characters (this is a Norton Guide limitation).
The $SYNTAX$ keyword should be followed by a CA- standard syntax specifier, such as:
$SYNTAX$
ft_screen( <nTop> [,<nBottom>] ) -> NIL
All parameters have proper prefixes (see paragraph 5.4), and are enclosed in <angle brackets>. Optional parameters are enclosed in [square brackets] as well. An arrow should follow, pointing to the return value. If there is no return value, it should be NIL. Any others should be preceded with the proper prefix (see the CA- Clipper documentation).
The $SEEALSO$ field provides a way to generate cross-references in the Norton Guide help documentation. Use it to point the user to other related functions in the forum toolkit. For example, if ft_func1() is also related to ft_func2() and ft_func3(), the field would look like this:
$SEEALSO$
ft_func2() ft_func3()
Note that fields are separated by spaces and the parentheses are included.
The $INCLUDE$ area allows you to specify what files are included by this function (this will be used to organize the on-line help file, and possibly the master makefile). An example would be
$INCLUDE$
int86.ch int86.inc
Other documentation fields should be self- explanatory. Review the appendix for a sample. All fields are required and must be filled in. Examples should not be considered optional.
5.1.4 Sample header and documentation block
Refer to the Appendix for a sample header and documentation block.
5.1.5 Test driver
A test driver is an optional section of C or CA- Clipper code that will only be compiled under certain circumstances. Developers are encouraged to include a short “test section” in front of their code.
The test driver shall be surrounded by the following pre-processor directives, and placed at the top of the source file:
#ifdef FT_TEST
[test code]
#endif
The test driver is currently optional, but authors submitting Clipper code should seriously consider adding it. It is a good way to include short demos within a piece of source code, yet pay no penalty because it is only compiled if needed. It will be invoked when a #define is created that says “#define FT_TEST.” This is a way for submitters to include short test routines with their functions and yet keep it all in one source file. This will be useful to end users.
This test driver may become required in a future version of the RFC.
5.1.6 Code
The source code shall be formatted as described in paragraph 5.4.
5.2 Function names
All NANFOR.LIB functions start with one of two prefixes. If the function is to be called by user programs, then it will begin with the prefix
FT_ ("F", "T", underscore)
Note that “FT” is a mnemonic for “Forum Toolkit.” If the function is “internal” to a module, then it will be prefixed by an underscore:
_FT ( Underscore, "F", "T" )
with no trailing underscore. Examples:
FT_CURDIR() "external" _ftAlloc() "internal"
5.3 Librarian’s authority to change function names
Some functions will be submitted that either (1) bear a similar name to another function in the library, or (2) bear an inappropriate name. For example, a function called FT_PRINT that writes a character to the screen could be said to be named inappropriately, as a name like FT_PRINT implies some relationship to a printer. The librarian shall have the responsibility to rename submitted functions for clarity and uniqueness.
5.3.1 Changing a function name after it has been released
Once the library is released with a particular function included, then a function name should generally be frozen and not renamed. To do so would probably cause difficulties with users who had used the previous name and are not tracking the changes to the library.
5.4 Source code formatting
5.4.1 Clipper
Clipper code shall be formatted in accordance with CA’s currently defined publishing standard. Although there will surely be some debate over whether this is a good idea, in general, the goal is to provide something consistent that all CA- Clipper developers will recognize.
Minor deviations will be permitted.
The CA standard usually means uppercase keywords, and manifest constants, and lower case everything else.
In addition, identifiers shall be preceded with the proper metasymbol:
n Numeric c Character or string a Array l Logical, or boolean d Date m Memo o Object b Code block h Handle x Ambiguous type
Refer to the CA-Clipper documentation for samples of CA’s code publishing format.
5.4.2 C
C source code shall be formatted in a generally accepted way, such as Kernighan and Ritchie’s style used in the book _The C Programming Language_.” The use of CA’s EXTEND.H is encouraged.
5.4.3 ASM
No particular formatting conventions are required for assembly language source code, since assembly code formatting is fairly standard. Lowercase code is preferred. Be sure to include the proper documentation header information, as described above.
Do not place ASM code in DGROUP. See paragraph 5.11.
5.5 Organization into .PRGs
Since many different people will be submitting routines, it is probably best if all routines that belong together are housed in the same .PRG. If there is some reason to split the .PRG, the referees and the librarian will handle that as part of library organization.
5.6 Header files
Including a “.ch” or “.h” or “.inc” file with each function would get unwieldy. For the purpose of NANFOR.LIB, all #defines, #ifdefs, #commands, #translates, etc that belong to a particular source file shall be included at the top of that source file. Since few submissions will split over multiple source files, there will usually be no need to #include a header in more than one place.
If a “ch” file will make the end user’s job of supplying parameters and other information to NANFOR.LIB functions easier, then it shall be submitted as a separate entity. The referees will decide on whether to include these directives in a master NANFOR.CH file.
5.7 Clipper 5.0 Lexical Scoping
NANFOR.LIB routines that are written in CA-Clipper will make use of CA-Clipper 5.0’s lexical scoping features to insulate themselves from the rest of the user’s application.
For example, all “privates” shall generally be declared “local.”
If a package of Clipper functions is added to the library, then the lower-level, support functions will be declared STATIC as necessary.
5.8 Use of Publics
Authors shall not use PUBLIC variables in NANFOR.LIB functions, due to the potential interference with an end-user’s application or vice versa.
If a global is required for a particular function or package of functions, that global shall be accessed through a function call interface defined by the author (.e.g, “ft_setglobal()”, “ft_getglobal()”, and so on). Globals such as these shall be declared static in the .PRG that needs them.
5.9 Use of Macros (“&” operator)
The use of macros in NANFOR.LIB functions will be, for the most part, unnecessary. Since this is a CA-Clipper 5.0 library, the new 5.0 codeblock construct should be used instead. Anyone having trouble figuring out how to convert a macro to a codeblock should post suitable questions on the CLIPPER forum on CompuServe.
5.10 Use of Static Functions
Any CA-Clipper 5.0 function that is only needed within the scope of one source file shall be declared STATIC. This applies mostly to NANFOR.LIB “internals” (names with an “_ft” prefix) that user programs need not access.
5.11 Use of DGROUP in ASM Functions
Use of DGROUP in assembly language functions shall be avoided, in accordance with CA’s recommendations. Assembly functions written for NANFOR.LIB shall use a segment named _NanFor, as in the following example:
Public FT_ChDir
Extrn _ftDir:Far
Segment _NanFor Word Public "CODE" Assume CS:_NanFor
Proc FT_ChDir Far . . . Ret Endp FT_ChDir Ends _NanFor
End
5.12 Use of "Internals"
Use of CA-Clipper “internals” by code authors is allowed. However, should any code make use of an internal, i.e., a function or variable that is not part of the published CA-Clipper API, then that internal shall be clearly marked in the documentation (under “DESCRIPTION”) and in the actual code, everywhere the internal is used.
5.13 Procedures for compiling functions
5.13.1 Clipper
Clipper functions will be compiled under the current release of CA-Clipper 5.0, with the following compiler options:
/n /w /l /r
Note that neither line numbers nor debugging information will find its way into NANFOR.LIB, to keep the code size down. End users may recompile NANFOR.LIB with these options enabled if they want to view NANFOR.LIB source in the debugger.
5.13.2 ASM
Assembly functions must compile successfully under any MSDOS assembler capable of producing the proper .OBJ file. However, care should be taken not to use any macros or special syntax particular to one vendor’s assembler, because that would make it difficult for end users to recompile the source. The preferred assembler is MASM, followed by TASM.
5.13.3 C
C functions must compile successfully under any C compiler capable of interfacing to CA-Clipper. Obviously, Microsoft C, version 5.1, is the preferred development environment. Care should be taken, when writing C code, not to use any special compiler features particular to one vendor’s C compiler, because that would make it difficult for end users to recompile the source.
5.14 Functions requiring other libraries
It is very easy to write functions in C that call the compiler’s standard C library functions. However, NANFOR.LIB can make no assumptions about the end user’s ability to link in the standard library or any other library. Therefore, no function will be added to NANFOR.LIB that requires any other third party or compiler manufacturer’s library.
6 ADMINISTRATIVE DETAILS
6.1 Librarian
The librarian will be the person who rebuilds the library from the sources and uploads the resulting deliverables to the proper CLIPPER forum library on CompuServe. The librarian generally does *not* test code or edit source code to repair formatting errors.
6.2 Documenter
The documenter is responsible for maintaining the Norton and guides and keeping it in sync with each new release.
6.3 Referees
Referees are volunteers who read source code, clean it up, compile it, look for problems like potentially problematic C code, decide on which function is best, consolidate common functions, etc. They make sure the header and documentation blocks are present. There is no election or term for refereedom. One simply performs the task as long as one can and bows out when necessary.
6.4 Transitions
Not everyone will be able to stay around forever to keep working on this project. Therefore, it is the responsibility of each referee, documenter, or librarian to announce as far in advance as possible his or her intention to leave, in order to give everyone a chance to come up with a suitable replacement. Don’t let it die!
7 CONTRIBUTORS
Current contributors, directly and indirectly, to this document include:
Don Caton [71067,1350]
Bill Christison [72247,3642]
Robert DiFalco [71610,1705]
Paul Ferrara [76702,556]
David Husnian [76064,1535]
Ted Means [73067,3332]
Alexander Santic [71327,2436]
Glenn Scott [71620,1521]
Keith Wire [73760,2427]
Craig Yellick [76247,541]
James Zack [75410,1567]
NOTES :
- In Harbour library file name of NanForum Toolkit is hbnf.a
- Maybe some functions :
- obsoleted,
- used some low-level hardware access or some OS specific features,
- so not included in hbnf library.
.OR. Logical OR
.OR.
Logical OR--binary (Logical)
------------------------------------------------------------------------------
Syntax
<lCondition1> .OR. <lCondition2>
Type
Logical
Operands
<lCondition1> and <lCondition2> are logical expressions.
Description
The .OR. operator is a binary logical operator that executes a logical
OR operation using the following modified Boolean rules:
. Returns true (.T.) if either <lCondition1> or <lCondition2>
evaluates to true (.T.)
. Returns false (.F.) if both <lCondition1> and <lCondition2>
evaluates to false (.F.)
Warning! In a departure from the Summer '87 and other dialect
behavior, Clipper shortcuts the evaluation of .OR. operands. This
means that <lCondition1> and <lCondition2> are both evaluated only when
<lCondition1> evaluates to false (.F.). If <lCondition1> evaluates to
true (.T.), the .OR. operation is true (.T.) and <lCondition2> is,
therefore, not evaluated. For backward compatibility, shortcutting can
be suppressed by compiling with the /Z option.
Examples
. This example shows .OR. results using different operands:
? .T. .OR. .T. // Result: .T. (shortcut)
? .T. .OR. .F. // Result: .T. (shortcut)
? .F. .OR. .T. // Result: .T.
? .F. .OR. .F. // Result: .F.
See Also: .AND. .NOT.
.NOT. Logical NOT
.NOT.
Logical NOT--unary (Logical)
Syntax
! <lCondition>
.NOT. <lCondition>
Type
Logical
Operands
<lCondition> is a logical expression to not.
Description
The not (!) operator is a unary logical operator that returns the
logical inverse of <lCondition>.
Examples
. This example shows .NOT. results using different operands:
? ! (.T.) // Result: .F.
? ! 1 > 2 // Result: .T.
? .NOT. 1 > 2 // Result: .T.
See Also: .AND. .OR.
.AND. Logical AND
.AND.
Logical AND--binary (Logical)
------------------------------------------------------------------------------
Syntax
<lCondition1> .AND. <lCondition2>
Type
Logical
Operands
<lCondition1> and <lCondition2> are logical expressions to AND.
Description
The .AND. operator is a binary logical operator that executes a logical
AND operation using the following modified Boolean rules:
. Returns true (.T.) if both <lCondition1> and <lCondition2>
evaluate to true (.T.)
. Returns false (.F.) if either <lCondition1> and <lCondition2>
evaluate to false (.F.)
Warning! In a departure from Summer '87 and other dialect behavior,
Clipper shortcuts the evaluation of .AND. operands. This means that
<lCondition1> and <lCondition2> are both evaluated only when
<lCondition1> evaluates to TRUE (.T.). If <lCondition1> evaluates to
FALSE (.F.), the .AND. operation is FALSE (.F.) and <lCondition2> is
therefore not evaluated.
For backward compatibility, shortcutting can be suppressed by compiling
with the /Z option.
Examples
. This example shows .AND. results using different operands:
? .T. .AND. .T. // Result: .T.
? .T. .AND. .F. // Result: .F.
? .F. .AND. .T. // Result: .F. (shortcut)
? .F. .AND. .F. // Result: .F. (shortcut)
See Also: .NOT. .OR.
