Release date(29/Mar/2005 19:24)


RSP RSP_C 1.0.0 b


RSP_C is a C language JIT ( just in
time compiler )

For the moment it is just a prototype , but fully
functional

It can execute source files as if it was already
compiled

The compiled ( cached ) file will not appear in the
folder where the source is located

The sintax to use the JIT is :

rsp_c file.c

The distribution includes file.rspc , to execute it
call :

rsp_c file.rspc

This is the Hello World ! application

By default the correct extension to rsp_c is .rspc but
it will compile any file as a C file

The errors are reported immediatelly , and if no error
occur then the file will execute

Files with extension .rspc will be associated with the
rsp_c.exe , then you can compile and execute the
source just typing the name of the .rspc file in the
console

Is up to you to use rsp_c.exe <file> or just <file>
at the console , both methods will work because the
application has a link in the Windows directory that
make it possible to call the rsp_c compiler from any
place in the system

For files without a extension .rspc , then you need to
insert the rsp_c.exe in front of the command

Any valid C file is a valid RSP_C file , but for the
moment only single files are supported , if you want
to use multiples files then include them using
#include in the source file like this

#include "file.h"

#include "file2.c"

The next release will have some directives that can be
added to the source file that will act like a makefile
, then defining commands with the directives you will
make it possible to modify the behaviour of the
compiler and include as many C files to the
compilation as you want

Notice that to the JIT only a single argument is
required , the next arguments are passed to the
compiled file as argument

Notice that passing commands this way :

rsp_c file.rspc file2.rspc

Will not compile both files but it will pass
file2.rspc to the file.rspc cache file as an argument

Remember , for the moment it is a single file
compiler, then you can pass only a single RSP_C file
plus arguments to the cached file

Future versions will have a makefile like method to be
embedded in the source file , in such a way to make
inclusion of other required files to the compilation
automatic

It has support to arguments to be passed to the
application

Calling it this way:

rsp_c file.rspc argument1 argument2
or
file.rspc argument1 argument2

Will pass argument1 and argument2 to the cached file
as if it was called this way:

file.exe argument1 argument2

It has support to up to 4 arguments , more arguments
will just not be passed to the executable

The initial path is the same where the source file is
located , it will execute as if the source file was
compiled to the path where the source file is located

The utilization of the JIT is very simple , just a few
possible arguments can be passed to the compiler ,
they are:

rsp_c /version

To get the version of the just in time compiler

rsp_c /cachedfiles

To see all the files that are in the cache

Any time a source file is passed to the compiler it
will create a cache of this file , and subsequent
calls to the same source file will execute the cache ,
then it will only compile when required

The detection of changes in the source is not based in
time , it is based on the checksum of the file

If the checksum is the same , then the cached file
will be executed

For each directory a different checksum will be
generated even from files with the same name

Then executing c:\back\file.rspc and
c:\backup\file.rspc will not refer to the same cached
file , but to two totally different files , the JIT
has a strong way to avoid this kind of colision

rsp_c /flush

To delete the files in the cache

It will remove all the cached files and directories
created by the JIT , to see the cached files go to the
path where the rsp_c.exe file was installed and you
will see a series of folders with hexadecimal names ,
each folder has a cached file on it , deleting it will
not cause problems , when the same source is compiled
again it will regenerate the cache file and folder



Operating System Compliance

Windows 95 , Windows 98 , Windows NT 4.0 , Windows
2000 , Windows XP



Install

To install the application just execute setup.exe and
follow the instructions

This software requires also the Mingw Full Version
installed

If you don't have Mingw gcc compiler installed then 
visit this page:
http://rspsoftware.8x.com.br/rsprspc.htm

And download mingw_full_3.4.2.zip

To install Mingw just execute mingw_full.exe and install
the package exactly in the same folder that you have 
installed RSP_C 1.0.0

In order to check whether the packages was correctly
installed just execute

rsp_c.exe

If the packages are correctly installed you will see a decription
of the usage of rsp_c.exe

If Mingw is missing or installed in an incorrect path it 
will be reported in the console this way:
"gcc not found or gcc error"

To uninstall the application , search for the package in
the add/remove applications in the controle panel ,
and select remove , it will remove the application
from the system


Documentation

The documentation is available online in the homepage


Homepage

http://rspsoftware.8x.com.br
http://www.geocities.com/rspsoftware1/

Homepage of the rsp_c compiler

http://rspsoftware.8x.com.br/rsprspc.htm
http://www.geocities.com/rspsoftware1/rsprspc.htm

Email

info@rspsoftware.8x.com.br
rspsoftware1@yahoo.com

Phone

#55 41 3276 7258

Thanks for using our software

RSP Software 1996-2006