SubSpace Biller 2 v1.12

[L.C.]

Name: SubSpace Biller 2

Download: http://www.hlrse.net/Qwerty/.ssb2-112/SSBilling2-v1.12.rar

Filesize: 288 KB

Author: Catid

Version: 1.12

Version Credits: RJ (rjscodingrealm.com), L.C. (bluetoast.org)

 

Release Changelog:

1.12 (Credits to RJ of rjscodingrealm.com and L.C. of bluetoast.org)
*All compiler warnings and errors fixed
*Converted to more modern code
*Fixed a bunch of the renamed commands that failed to work correctly
*Slightly revised subbill.ini
*Increased byte limit to 10 bytes from 9 bytes on ?recyclezone and ?closezone to prevent the biller from crashing due to a memory violation or buffer overflow
1.11k
*Renamed 'c-' in any command to 'chat'
*Renamed 'welcome' in any command to 'greet'
*Renamed ?login to ?blogin
*Renamed ?man to ?bhelp
*Renamed the whole set of messaging commands to something easier to remember

 

Summary of Changes:

Basically a bunch of bugs and problems were fixed with the biller and it will now (or should) compile with 0 errors and 0 warnings. Many parts of its code were converted to more modern functions, etcetera. RJ did most of the work in my opinion, while I did what I could with whatever knowledge and experience I have with looking at programming code.

 

This compile has not been thoroughly tested for additional bugs, so please report them so that they may be fixed.

 

SSBilling2_v1.12.rar

[CRe]

Interesting..

[»Purge]

Should this release run faster?

[L.C.]

Should this release run faster?

I would think so since it compiles with no errors or warnings and parts of its code were converted over to more modern functions and such, versus 1.11j running with several compile warnings and stuff. To my understanding, having no errors and warnings means the program will be more reliable, secure, and/or stable (does not mean that there will not be bugs though).

 

I won't switch BlueT over to this version until I have personally tested it thoroughly and/or I receive good reports about it and minimal or no problems (bugs).

Edited June 1, 2008 by L.C.

[»doc flabby]

I won't switch BlueT over to this version until I have personally tested it thoroughly and/or I receive good reports about it and minimal or no problems (bugs).

Will you do a linux port too? I noticed that you are using (or at least it says in the wiki) my (quick and dirty) port of catid's original.

Edited June 1, 2008 by doc flabby

[L.C.]

I noticed that you are using (or at least it says in the wiki) my (quick and dirty) port of catid's original.

Yeah. BlueT is using your Linux port of v1.11j at the moment. v1.12 will have to run through Wine on BlueT unless I get a port out on the block.

 

EDIT :: I'll likely end up playing around with your code and comparing it to v1.12's code. Then if it looks safe enough, would mix the v1.12 with your port and get an equivalent available.

 

I did ask RJ how hard it would be to make a genuine Linux port. He said it would not be hard but would take some time; he isn't really interested at the moment in finding the equivalent code functions and such (in comparison of the Win32 API to Linux). Maybe sometime later though.

Edited June 1, 2008 by L.C.