NSBasic and compiled languages are very different. Compiled languages use compile-time type checking. NSBasic is a compiled/interpreted language with a mixture of compile-time and dynamic types. Due to this, you must take some care according to certain rules when building and using libraries. You cannot use just any old library with NSBasic. Fortunately, if you have a library that does not follow the rules, you can always write another library which is just a wrapper around the difficult library.

Libraries can be written in many systems including CodeWarrior and GCC, and a Pascal example is provided at the end of this tech note. Most libraries for NSBasic have been written in C under CodeWarrior, and the majority of this tech note refers to CodeWarrior.

NSBasic uses conventions derived from the excellent MathLib library. They are as follows:

• Each function must return a value of type Err. This value should be zero unless there is a catastrophic failure within a call to the library, in which case it may return an error code. This code is currently ignored by NSBasic, but this may change in the future.
• The first parameter to each function in a library must be an Int16 or UInt16 reference number. This is standard practice for libraries.
• The parameters to the function must start immediately after the reference number.
• If the function is to return a value and be used as an NS Basic function, it must return the value through a pointer parameter, which must be the last in the list.
• The Open and Close functions must be as follows:
  

  Err OpenFunction(UInt16 refNum, UInt16 version) 
  Err OpenFunction(UInt16 refNum)
  Err CloseFunction(UInt16 refNum, UInt16 *useCount) 
  Err CloseFunction(UInt16 refNum)

  The second form is preferred, but NS Basic will work with both.

There are two tasks to complete when writing a library. One is to write the information file. The other is to write the library itself. If you are adapting an existing library that satisfies the conditions above, you will only need to write the information file.

Writing the Information File

The information file for a library provides information for the NSBasic IDE to determine how to call the library. Its name always ends in .inf and it resides in the Lib subdirectory of the NSBasic install directory (e.g. C:\NSBasic\Lib).

There are two versions of information files. Version 2 is recommended for all new development and is the only version described here.

A simple information file might look something like this:

[General]
ExtensionName=Test-library
PrcName=TestLib.prc
Version=2.0 Beta
Manufacturer=NSBasic.com
InfVers=2.0

=HelpStart=
""
"Test Library"
""
"This library is just a test"
=HelpEnd=

[GlobalMethods]
Multiply=1,func,2,"Multiply(in a as double, in b as double) as double"
ChangeStatus=2,proc,1, "ChangeStatus(in a as integer)"

Each line consists of several fields. First is the name of the function or subroutine, separate by the index with an equals sign. The index should start as 1 and be incremented for successive lines. Then there is the word func, indicating a function that returns a value, or proc, indicating a subroutine. Next is the number of parameters to the subroutine or function. Finally there is a description of the function or subroutine.

The function or subroutine description looks much like a declaration in NSBasic, with a few twists to give the compiler important information. Consider the ChangeStatus subroutine:

ChangeStatus(in a as integer)

This specifies a subroutine that takes one parameter. "In a as integer" means that there is a parameter, a, which is an Integer. It also specifies that this is an in parameter. There are three kinds of parameters: in, out, and inout (one word). In parameters are used when a value should just be passed to the library function by value. In the case of in arguments, the C code of the library expects a simple type such as double or Int16. Out and inout parameters are used when a value must come out of or go in and come out of a library function. In the case of out and inout arguments, the C code expects a pointer to a type, such as double* or Int16. String and Byte parameters are always passed by pointer.

Type names are not case sensitive.

To make information files accessible both to people who prefer C and to people who prefer NSBasic, some types can be specified in many ways:

Many examples of information files are provided with NSBasic.

Writing the Library

Writing a library for NSBasic is no more difficult than writing any other library.

One of the best ways of writing a library is to start with the MathLib library. Source to this library is freely downloadable. See http://www.radiks.net/~rhuebner/mathlib.html

You can also write a library using CodeWarrior's library wizard. This requires that you define all of the functions and subroutines beforehand, as it is awkward to change them after the project is created.

We will use the example of a simple base conversion package called Cnv. It will contain two functions to convert positive to different bases, such as binary and hexadecimal, and vice-versa. We will start the design by imagining how we want to use the library in NSBasic:

Dim s As String
Dim n As Integer
s = Cnv.DecToBase(37, 16)     's will be 37 in base 16
n = Cnv.BaseToDec("177", 8)   'n will be the value of 177 in octal
s = Cnv.DecToBase(42, 10)     'Works like Str for positive integers

When the input is out of range, DecToBase will return a blank string, and BaseToDec will return -1.

Creating an information file is straightforward:

[General]
ExtensionName=Base-Conversion-Library
PrcName=Cnv.prc
Version=1.0 Alpha
InfVers=2.0
Manufacturer=myself

[GlobalMethods]
DecToBase = 1, func, 2, "convertedValue = DecToBase(in n as integer, in base as Integer) as String"
BaseToDec = 2, func, 2, "decValue = BaseToDec(in s as String, in base as Integer) as integer"

Now to create the project, start up CodeWarrior and close any files it may remember from the previous session. Pull down New... from the File menu. Make sure the Project tab is chosen. Select Palm OS Library Wizard, enter Cnv in the Project name field, choose an appropriate destination, and press OK.

You will then see a window with four fields. The default values for all four fields will work. For production work, it is srtongly recommended that you get a unique creator ID from Palm at this point. The process is free and painless; just press the Visit Creator ID Website and follow the directions. However, as this is to be used for testing purposes only, we can leave the creator ID as STRT. Press the Next > button and dismiss the warning dialog window that comes up.

Now you will see a window for adding function names. Enter all the functions and procedures in your .inf file in order. Press Add and type DecToBase. Press Add again and type BaseToDec. Press Next >.

You will see a window with a list of libraries to add to your project. Most libraries do not need to call other libraries. Many of these libraries will not even work within libraries. Simply press the Finish button. A new project will appear.

It has also provided stubs for your the two functions to implement, CnvDecToBase and CnvBaseToDec. (Even though you may have functions and procedures for NSBasic, C uses the word "function" to describe both, and they are implemented the same way.

Take a look at CnvDecToBase. It is declared like this:

Err CnvDecToBase(UInt16 refNum)

To start implementing this function, we look back at the line in the .inf file:

convertedValue = DecToBase(in n as integer, in base as Integer) as String

Argument 1: An Int32
Argument 2: An Int32
Return value: A char *

Err CnvDecToBase(UInt16 refNum, Int32 n, Int32 base, char *retVal)

extern Err CnvDecToBase(UInt16 refNum, Int32 n, Int32 base, char *retVal)
	CNV_LIB_TRAP(sysLibTrapBase + 5);

decValue = BaseToDec(in s as String, in base as Integer) as integer

Err CnvBaseToDec(UInt16 refNum, char *s, Int32 base, Int32 *retVal)

extern Err CnvBaseToDec(UInt16 refNum, char *s, Int32 base, Int32 *retVal)
	CNV_LIB_TRAP(sysLibTrapBase + 6);

Now the only thing left to do is implement the actual functions. Here is one possible implementation, which can be typed or pasted into CodeWarrior, replacing the stubs provided by the wizard:

Err CnvDecToBase(UInt16 refNum, Int32 n, Int32 base, char *retVal)
{
	#pragma unused(refNum)
	
	if (n < 0 || refNum < 2 || refNum > 32)
	{
	    /* Bad parameters */
	    StrCopy(retVal, "");
	    return errNone;
	}
	
	*retVal = '\0';
	do
	{
	    char *s;
	    char remainder;
	    
	    /* Open up a space for the next digit */
	    for (s = retVal; *s; ++s){}
	    for (++s; s > retVal; --s)
	    {
	        *s = *(s - 1);
	    }
	    
	    remainder = n % base;
	    
	    if (remainder < 10)
	    {
	        *retVal = '0' + remainder;
	    }
	    else
	    {
	        *retVal = 'A' + (remainder - 10);
	    }
	    
	    n /= base;
	} while (n > 0);
	
    return errNone;
}    


Err CnvBaseToDec(UInt16 refNum, char *s, Int32 base, Int32 *retVal)
{
	#pragma unused(refNum)
	char *runner;
	
	*retVal = 0;
	
	if (base < 2 || base > 36)
	{
	    /* Bad parameters */
	    *retVal = -1;
	    return errNone;
	}
	
	for (runner = s; *runner; ++runner)
	{
	    UInt16 digit;
	    
	    if (*runner >= '0' && *runner <= '9')
	    {
	        digit = *runner - '0';
	    }
	    else if (*runner >= 'A' && *runner <= 'Z')
	    {
	        digit = *runner - 'A' + 10;
	    }
	    else if (*runner >= 'a' && *runner <= 'z')
	    {
	        digit = *runner - 'a' + 10;
	    }
	    else
	    {
	        *retVal = -1;
	        return errNone;
	    }
	    
	    if (digit >= base)
	    {
	        *retVal = -1;
	        return errNone;
	    }
	    
	    *retVal = *retVal * 10 + digit;
	}
		
    return errNone;
}

It is considered good practice in NSBasic libraries to include a 'tver' resource with ID 0 consisting of a string with the version number (in this case, "1.0 Devel"). However, CodeWarrior tries to prevent additional resources from being added to libraries. Use one of the free, downloadable editors available on the Palm developer web site to add this resource after the file has been created. Now we need to use and test the new library in an NSBasic program.

First create a new project to test it. In the Startup Code, insert this line:

   LoadLibrary Cnv

We're going to make a simple decimal to hexidecimal converter. Create two text fields, one called Dec and the other called Hex. Then create a button. Within the subroutine of the button, insert these lines:

Dim ins as String
Dim in as Integer
Dim outs as String

    ins = Dec.text
    in = Cnv.BaseToDec(ins, 10)
    outs = Cnv.DecToBase(in, 16)
    Hex.text = outs

Test the new project by running it. If you successfully installed the .inf file, it should compile. However, when it runs, it should produce an error message because the library has not been loaded.

Add Cnv.prc to your NS Basic project as a resource, with type set to 'libr'. It will then be included in the .sisx file and installed.

Now it should work. Enter a decimal number into the Dec field and press the button. Its hexadecimal equivalent should appear in the Hex field.

Any number of libraries may be embedded in the application.

Right-click on the Resources folder and choose Add Resource. Navigate to Cnv.prc, select it, and press Open. A new resource will be added. Change the Resource Type to libr and the name to Cnv and recompile. You may note that the size of the project is a little bigger. This is because the library is now present in the project.

Tricks with Strings

The problem with changing and returning strings is that, in normal C code, the called function has no way of knowing how much memory is allocated to the string. The library code ensures that there are at least 300 bytes or the size of the previous returned string, whichever was longer. However, this is not enough for some applications.

Trick 1: Resizing Handles

Trick 1 is most useful when the string is to be made on the fly based on the input data.

Consider Yuk rewritten this way:

/**
	Yuk generator after Doug Lee
	Returns a sentence of in Yuks

    Yuk(3) => "Yuk, yuk, yuk."
    Yuk(1) => "Yuk."
  */
Err Yuk(UInt16 refNum, short in, Char *ret)
{
    char *s;
    int k;
    
    if (in <= 0) return 0;
    
    /* NEW CODE */
    {
    	MemHandle m = MemPtrRecoverHandle(ret - sizeof(Char *));
    	MemHandleUnlock(m);

    	if (0 != MemHandleResize(m, in * 5 * sizeof(Char) + sizeof(Char *)))
    	{
    	    ErrFatalDisplay("Resize failed in Yuk.");
    	}
    	
    	s = MemHandleLock(m);
    	*((Char **) s) = s + sizeof(Char *);
    	s += sizeof(Char *);
    }
    /* END NEW CODE */
    
    for (k = 0; k < in; ++k)
    {
        if (k)
        {
            *s++ = ',';
            *s++ = ' ';
        }
    	*s++ = k ? 'y' : 'Y';
    	*s++ = 'u';
    	*s++ = 'k';
    }
    *s++ = '.';
    *s = '\0';
    
    return 0;  // No error
}

    	MemHandle m = MemPtrRecoverHandle(ret - sizeof(Char *));

    	MemHandleUnlock(m);

    	if (0 != MemHandleResize(m, in * 5 * sizeof(Char) + sizeof(Char *)))
    	{
    	    ErrFatalDisplay("Resize failed in Yuk.");
    	}

This is only an example; production code should probably have more graceful error recovery than just a fatal display.

    	s = MemHandleLock(m);

    	*((Char **) s) = s + sizeof(Char *);

    	s += sizeof(Char *);

Trick 2: Changing Pointers

Trick 2 is useful when the return string is fixed in memory and will not change at least until the next library call. Perhaps the string is in a database. Perhaps it is some string that is managed by the library in some sort of "global" string.

Here is Yuk rewritten this way:

**
	Yuk generator after Doug Lee
	Returns a sentence of in Yuks

    Yuk(3) => "Yuk, yuk, yuk."
    Yuk(1) => "Yuk."
  */
Err Yuk(UInt16 refNum, short in, Char *ret)
{
    char *s;
    int k;
    
    if (in <= 0) return 0;
    
    ret -= sizeof(Char *);
    * ((Char **) ret) = HaveSomeYuks(in);
    
    return 0;  // No error
}

HaveSomeYuks is deliberately undefined, but it should be a function that returns a pointer to some static string.

As part of the return process, this string will be copied into an NSBasic string. However, for long strings, at least this way of writing the function does not use up extra temporary memory beyond this.

A Library Example

Contributed by Ron Glowka.

[Note: This contribution was written when only Version 1 information files were available. Some of the limitations have been removed. -Ed.]

First, you should download the sample Library example project and the NSBasic test program which calls it.

• The first zip file contains the .prc files and the NSBasic project.
• The second zip file contains the Library source code and project files for CodeWarrior version 7.
• The third zip file is the same as the second, except it is for CodeWarrior version 9 (thanks to M. Edward Wilborne, III.)

I adapted this example from the Library example that comes with CodeWarrior v7. I removed a bunch of stuff that wouldn't be needed for an NSBasic Library and I rearranged the code to have all the custom code together and put all the "Standard/Required" code, that you don't need to modify, at the end of the files where you can easily "ignore" them.

This project is meant to be a template for creating other Libraries. It really doesn't do much of anything useful but it should serve as a good starting point. The examples I adapted this from all had function names, variables, structures, etc. that identified a specific library (example: MSLfunc1 (MSL for MySharedLib)). I changed all these to start with the word "THIS_". Anything starting with "THIS" means that it belongs to "this" library. Since this example is only meant for use with NSBasic programs, you can safely leave the "THIS" in your own libraries because NSBasic uses the information in the .inf file and not any identifiers in the code itself. If you need to access your library from a C program, then you will need to try to make unique public identifiers.

The source code and project names also start with "THIS". These too, can be left as is in your own libraries if you separate your libraries into separate project directories. Besides your custom code, all you really need to do is to change the "Targets" settings for the "PalmRez Post Linker" in CodeWarrior to have the correct Output File Name and Creator Id.

I tried to make this example both simple and comprehensive enough to be useful. Global and static variables can not be used in a Library, but globals can be "simulated". This complicates the code somewhat, so I put the global routines in a separate file where they don't have to be looked at unless needed. Even then, all that should be required to use globals is to add your global definitions to the "globals" structure and initialize them if necessary - everything is already initialize to 0's.

You probably really need to look at the project before the above comments make a lot of sense...

To use the Library from NSBasic, you need to make sure that the "SLExample.inf" file is in your "nsbasic\lib" directory. Then, take a look at the NSBasic test project, SLTest.prj, to see how it is using the library. The files you need to put into your installer are SLExample.prc and SLTest.prc. SLExample.prc is the library and will not show up on your application launcher because of its "libr" database type.

The functions in the library example are fairly straight-forward. The FldGetSelection... functions use global variables. This is because only one non-string variable type can be returned from a library function. FldGetSelection returns both the start and end positions of a selected area in a field. So, the Library example breaks this into 2 functions; FldGetSelectionStart and FldGetSelectionEnd. The FldGetSelectionStart function retrieves both the start and end positions, stores both in "global" variables, but only returns the start position. The FldGetSelectionEnd function only accesses the globals, and returns the end position stored there by the FldGetSelectionStart function.

Interesting Things I Learned:

• Like SysTraps, strings passed as parameters must be initialized to their maximum expected size before calling the library function.
• UNLIKE SysTraps, strings returned as function values do not need to be initialized. This is WAY COOL!
• You can return multiple strings as parameters, but you can only return 1 non-string type (double, int); and, it must be the return value of a function.
• The example function "DelimitedItem" which parses a string for items delimited by a specific delimiter (ie. ",") was over 10 times faster in a library than in equivalent code in NSBasic.

I'm sure I could have said a lot more, but check this stuff out. Disect the Test program and the Library code. I'll be happy to answer any questions I can.

Ron

A Pascal Compiler Library Example for NSBasic

This very small and simple tech note is meant to be a template for creating other Libraries using free PalmOS Pascal Compiler. This project really doesn't do much of anything useful but it should serve as a good starting point. You will see that it is *very* easy to create a SL for NSBasic using PP Compiler.

First, you should download the needed files:

1) PPNSBasicLib.pas - It's our PP source code in Palm DOC format (PDB).
2) PPNSBLibTest.prj - It's our NSBasic project to test our new SL.
3) PPNSBLib.inf - It's our "inf" file, describing each function as an interface between SL and NSBasic.
4) PP Compiler Enviroment - It's a merged enviroment in a SSF file.

You can download all of them clicking here (252 Kb).
You can see a brief description of them here.

I adapted this example from the Library example that comes with PP Compiler.
If you wish to take a look at PP source code before continue reading, click here.

As I said, it is meant to be a template for other SL and you will verify that is quite simple to insert your own functions using this template.

The two functions in the library example demonstrate just an addition and a multiplication. I tried to make this example both simple and comprehensive enough to be useful.

Important: Anything starting with "THIS" means that it belongs to "this" library. Since this example is only meant for use with NSBasic programs, you can safely leave the "THIS" in your own libraries because NSBasic uses the information in the .inf file and not any identifiers in the code itself.

In order to make things straight forward our objectives, I created a special PP Compiler enviroment using a SSF file that you can open with your PalmOS Simulator. Last version should be installed with NSBasic 4.0. If you don't have Simulator 5.3, please, download it here.

As soon as you have it running, you would see these three icons in "Unfiled" category: Piaf, PP Shell and PPNSBLibtTest.

Following these screenshots, you will be able to compile your first Library. After, using some Pascal knowlegde, you will be able to, sooner than you can imagine, try some modifications or even a total new Library. Hope you share it with us :)

Later, if you wish to create your own PP enviroment, using your own Palm device, for example, just follow this link. Or, if you wish to edit your SL in a Windows IDE, you may use Fozzy.

There are some curiosities, just in case you would like to know. You don't need.

Well, that is enough to get started. Don't forget to study our template. Print it as a quick reference.

Descriptions

Some ScreenShots that may help

Screenshot 01 After starting Piaf, click on "O" and choose PNSBasicLib.pas. Click OK.	Screenshot 02 You should see this source code.
Screenshot 03 These lines show the two simple functions Add and Mul. Here you can see the Library name too.	Screenshot 04 Here, you see the last lines of our Library. Add and Mul are the last ones, after Open, Close, Sleep and Wake (internal functions - don't worry about them - just KISS)
Screenshot 05 To compile, just click on "B". It took 0.32 seconds to compile 568 lines in my computer.	Screenshot 06 Next step: Go to Launcher Applications menu and choose "Copy...".
Screenshot 07 Choose PPNSBasicLib. Verify that "Copy To:" is set to POSESlot1, your simulated Expansion Card. So, look at \Card1\PALM\Launcher\ folder in your Simulator folder. PPNSBasicLib.prc should be there after "Copy".	Screenshot 08 Are you read to test? Start our PPNSBLibTest program. That one you compiled in NSBasic.
Screenshot 09 Choose your numbers and get a MUL result	Screenshot 10 Choose your numbers and get an ADD result

Some curiosities

Curiosity 1 Q.: But, how is PPNSBasicLib inside? A.: It just has our famous "libr" resource	Curiosity 2 Q.: And PPNSBasicLib.pas? A.: It is just a Palm DOC file, with a header and our Pascal source code in the second record. If you wish, you may open this file in any Palm DOC reader.
Curiosity 3 As I said, here it is our Pascal source code...	Curiosity 4 Here, we have an inside view of our PPNSBLibTest program created with NSBasic.

Fozzy is a free IDE for PP Compiler. You may download the latest version here.

After that, you will be able to start creating your own libraries.

Good luck ! (You won't need :)

Adrian Nicolaiev
http://www.niconnect.com