Last update : sexta-feira, março 31, 2006 11:36:35
RSP RSP_C 1.0.0 b
(30/Mar/2005 23:03)
To know more about the RSP_C 1.0.0 JIT compiler read the FAQ
What is new
The first helper tool to RSP_C will be available soon (31/Mar/2005 12:35) : The RSP_C JIT compiler is not just a simple compiler , the next release will have runtime code protection that can detect at runtime common C programming problems and the first application to deal with these problems is about to be released , his name is Doctor Junior , this application will catch runtime errors occurred with a RSP_C based compiled code , the information will explain what problem was detected including source code file and line , like this tool several other tools will be release releated to RSP_C
Version 1.0.0 b is available (30/Mar/2005 23:03) : Version 1.0.0 b was released to fix some bugs of the version 1.0.0 , it now has all the required headers and libraries to compile win32 based applications
First RSP_C bug (30/Mar/2005 14:20) : First bug found on the RSP_C 1.0.0 , the bug occurs if you need to use stdin , the application running will receive it but will only show the value entered in the end of the application , the problem occurs because the output of the cached file was being redirected to a pipe , so , it is not received by the console at the same time it was entered , this is a file to reproduce the problem ,and this problem is already fixed in the version 1.0.0 b available to download in the bottom of this page , notice also that the version 1.0.0 b has both ansi C and win32 headers and libraries , while the first version released has only the ansi C libraries
The new RSP_C 1.0.0 JIT compiler is alive and kicking (30/Mar/2005 07:54) : The first version is available to download , this is just the first step , at this moment it is a prototype but fully functional
It can compile on the fly C language source and execute it as if it was already compiled , like any other script language
The name was changed from c_script to RSP_C to avoid colision with the cscript.exe application that is part of Windows XP (apparently)
The version 1.0.0 is just 3.1 megabytes of size including a fully functional C compiler modified to work as a JIT
The installation of the package will not affect any other compiler installed because it has their own environment
It don't requires any other package that is not in the distribution
After the installation you have a fully working scripting language based on C
A new programming environment (28/Mar/2005 00:29) : Thinking about the problem that we have today with the development languages we decided to enter this world creating a new whole development environment
In this environment we hope to solve some of the problems that programmers have today with Java , VB , .Net framework and other environments
1 - It is driven to performance
2 - It provide support to script and native compiled executables , but both at execution time will run as optimized native win32 code ( future support to Linux )
3 -You will be able to create components in the same way you create components in Visual Studio
4 - Compiled code is protected against tampering , if it isnot the original compiled code , then the whole application will not run
5 - It is directly based on C , without adding any other feature that is not compliant with C , the minimal modifications to be added to the script or source code can be quickly modified to make the script or source compilable in any ansi C compiler
6 - It provides a JIT in the same way other environments provide today , with one advantage , if the script is compiled then no runtimes distribution required , and it will run in any machine without any other requirement
We hope to release the first beta of this environment in less than a month
The name of this environmet is c_script and it is based in Mingw , the free win32 gcc compiler
Description
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
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 as :
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
For more information read the FAQ
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 3.4.2 installed
If you don't have Mingw gcc compiler installed then download it below
The file to download is 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"
This is a screenshot of the folder where RSP_C is installed
To uninstall the application , search for the package in the add/remove applications in the control panel , and select remove
Or locate unist.exe and unist_mingw.exe in the folder where RSP_C was installed and execute it
Download
Size 102,135 bytes
MD5 checksum 6e8db7955e11d7a27b33bcc3ae0acc28
Version 1.0.0 b requires this package installed also
Size 3,714,356 bytes
MD5 checksum de16edc8eaed1089cbd29291407493ed
RSP_C 1.0.0 (removed)
Size 3,174,870 bytes
MD5 checksum 98e938329ac229ae467ca5098ce2fbbc