|
Run Agena Scripts Easily (rase) v. 7.7.0.4 (5/7/2026, Alexander Walz) |
Readme/What's new |
rase - Run Agena Scripts Easily in Windows NT 4.0 or later and in OS/2.
Please refer to the explanations in `example.agn`.
For a quick demo, unpack all the files into a new, fresh directory, change into this directory and run the `example.exe` file
in an command shell (Windows) or `example.cmd` (OS/2) as follows:
example 1 2
There is also a utility called `whereis` which searches for a file in a path:
whereis /r /a "agena.*" c:/agena
Another one prints drive information:
drive c:
Finally, a script printing information on installed memory:
memory
In your operating system, you may want to add the path to the rase directory to your PATH system environment variable.
Credit: The implementation is based on https://www.cs.usfca.edu/~galles/cs420/lecture/LuaLectures/LuaAndC.html,
written by: Associate Professor David Galles, Department of Computer Science, University of San Francisco, CA 94117.
For compilation hints, check the top of the rase.c source file.
----------------------------------------------------------------
# READ.ME and DEMO Run Agena Scripts Easily (rase) for Windows
/*
This file shows how to execute Agena scripts in Windows NT 4.0 and later without passing the script and its arguments
to the actual Agena interpreter.
We won't call "agena example.agn 1 2" from the commandline, but just enter "example 1 2" in the NT shell.
In OS/2 we use the batch script example.cmd to execute a script.
Please make sure that the following files are now in one and the same directory:
example.agn (or your favourite script filename)
example.exe (Windows only, or your favourite executable filename)
agena.exe (in OS/2 only)
agena.dll (do not change the filename)
library.agn (do not change the filename)
libgcc_s_dw2-1.dll (Windows only, do not change the filename)
libmingwex-4.dll (Windoes only, do not change the filename)
In Windows, rename the following files in this ZIP file to your favourite name:
example.exe -> yourfavouritename.exe
example.agn -> yourfavouritename.agn
In OS/2, rename the following files in this ZIP file to your favourite name:
example.cmd -> yourfavouritename.cmd
example.agn -> yourfavouritename.agn
and edit the *.agn file according to your need. The *.exe or *.cmd file will launch your *.agn script file of the same name.
For a more elobarate script that locates files, links or folders in a directory, check the `whereis.agn` script.
For a script that prints drive information, check the `drive.agn` script. */
print('\nDemo using NO explicit function by referring to the \`args\' table:');
print('-----------------------------------------------------------------\n');
print('Number of arguments:', size(args));
# all arguments (all strings )are available in the args table, including the name of the script at index 1
print('Arguments passed: ', args);
# we convert the command-line arguments to numbers
local x, y := tonumber(args[2]), tonumber(args[3]);
if x :: number and y :: number then
print('Test: ', x & ' minus ' & y & ' is ' & (x - y));
print('Test: ', 'sqrt(' & x & ' + ' & y & ') is ' & sqrt(x + y))
fi;
/* In Windows, we _alternatively_ define a function of the same name as the executable
(w/o the file suffix, `example` in this case). This function will then be called
by the executable `example.exe`.
Just enter the following statement in an NT shell (cmd.com) and see what will happen:
example 1 2
*/
example := proc(?) is # this function will be automatically called by the executable
print('\nDemo using explicit function of same name \& \`nargs\' and the \`varargs\' table:');
print('----------------------------------------------------------------------------\n');
print('Number of arguments:', nargs);
print('Arguments passed: ', ?);
local x, y := tonumber(?[1]), tonumber(?[2]);
if x :: number and y :: number then
print('Test: ', x & ' minus ' & y & ' is ' & (x - y));
print('Test: ', 'sqrt(' & x & ' + ' & y & ') is ' & sqrt(x + y))
fi
end;
/* The output should be:
C:\agena\extract>example 1 2
Demo using NO explicit function by referring to the `args' table:
-----------------------------------------------------------------
Number of arguments: 3
Arguments passed: [example, 1, 2]
Test: 1 minus 2 is -1
Test: sqrt(1 + 2) is 1.7320508075689
Demo using explicit function of same name & `nargs' and the `varargs' table:
----------------------------------------------------------------------------
Number of arguments: 3
Arguments passed: [example, 1, 2]
Test: 1 minus 2 is -1
Test: sqrt(1 + 2) is 1.7320508075689
*/
|
|
Agena v. 7.7.0 (30/6/2026, Alexander Walz) |
Readme/What's new |
agena >>
`The Power of Procedural Programming`
7.7.0 Ariel, June 30, 2026
- The `@` mapping operator did not process strings. This has been fixed. The return is a sequence of the mapping results.
Example to convert a string to ASCII codes:
> <: x -> abs(x) :> @ '12345':
seq(49, 50, 51, 52, 53)
The operator has also been tuned by 31 %.
- Likewise, the '$' selection operator now processes strings. Example:
> s := '01234567890123456789012345678901234567890123456789';
> f := <: x -> x < '5' :>;
> f $ s:
0123401234012340123401234
The operator has also been tuned by 33 %.
- The `$$` selection and `$$$` counting operators could access invalid memory when under high load. The `$$` operator
also wrongfully called the `in` metamethod if it was attached to the structure to be scanned. This has all been
fixed.
The `$$` and `$$$` operators work with strings now. While `$$` has become 7 % faster, `$$$` has become 2 % slower.
- This release has been Valgrind-checked on x86 and x64 Linux to ensure there are no internal errors or memory leaks. |
|
Agena v. 4.12.5 (20/5/2025, Alexander Walz) |
Readme/What's new |
4.12.5 Merryville, May 20, 2025
- In the past, the bitshift operators <<< (left shift), >>> (right shift), <<<< (left rotation) and >>>> (right rotation) had different behaviour across platforms when a number at or beyond the +/-2^32 threshold has been processed. This has been changed and the results in these situations are now the same.
Likewise, `bytes.numto32` is now returning the same results on all platforms when casting a value at or beyond the +/-2^32 border.
This also benefits various functions in the `hashes` package as their returns are now the same across platforms, as well.
To check the new underflow or overflow behaviour, use `math.wrap`.
- New function `math.fmod` works and returns the same result as the binary `symmod` operator. It has just been added to facilitate porting C code to Agena.
- The results of `hashes.mix`, `hashes.crc32`, `hashes.crc8`, `hashes.reflect`, `hashes.parity`, `hashes.fibmod`, `hashes.interweave`, `hashes.jinteger` may now be different with out-of-range input, that is with arguments at or beyond the 2^32 threshold, depending on your platform. |
Comments
Alexander Walz
Sat, 13/05/2017 - 20:06
Permalink
Hello,
Add new comment