Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Feb 18, 2013 22:25:14 GMT 1
It almost sounds easier to start over from scratch. I think I'll have another look at the _nocat project after 2.0 is released for beta. Thanks for all the cool stuff!
|
|
|
Post by Pjot on Feb 19, 2013 10:07:00 GMT 1
Well, I said that I can almost rename it to 2.0 But as there are no severe changes in the functionality of BaCon (only in the implementation) I guess it is better to stick with the current numbering... BR, Peter
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Feb 19, 2013 20:47:06 GMT 1
1.1 ?
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Mar 30, 2013 16:04:25 GMT 1
Good to see that BaCon is getting better and better! Just downloaded 1.0.29 and it seems to convert HUG programs much faster than the older versions. And yes, renaming would be a good idea (I agree with jrs - 1.1 looks much better than 1.0 build ...).
|
|
|
Post by Pjot on Mar 30, 2013 19:05:17 GMT 1
Folks, A new stable release of baCon is about to hit the internet. It is scheduled for April 1 (no joke, really). As mentioned, this new version comes with a more effective (=faster) memory management, which eventually resulted in a relatively small change, but which took almost 2 weeks to investigate and develop. It also contains a complete revision of the major string functions and a complete rewrite of the error messaging. Next to that, the code of all BaCon versions has been aligned to guarantee the exact generation of source files. By precise line-by-line checking, a lot of small glitches and code errors were detected and fixed. Along the way, with the help of you forum members, bug reports came in and were fixed. The overall performance of the generated code has increased, of course depending on what kind of program is being compiled. Compiling BaCon using BaCon now performs about 30-35% faster - maybe even faster, as the bottleneck now is the I/O of my harddisk. For the version numbering, I gave it a second thought. More people have mentioned that I should increase it. Though for us, programmers, the whole concept of version numbering may look somewhat superfluous when it comes to determining 'maturity' or 'stability', I thought the upcoming release indeed may be a good opportunity to go to BaCon 2.0. The huge overhaul of the code in this last version, the large list of changes, the thorough testing on other platforms, the steady amount of reports from the forum members and the accompanying suggestions and fixes certainly justifies to this step, even though there were no changes in the API at all. Currently, I am updating the documentation and performing some final tests. If all goes well then BaCon 2.0 will appear on the website this Easter. Best regards Peter
|
|
|
Post by konaexpress on Mar 30, 2013 20:42:33 GMT 1
Way to go! Good luck with this.
-John
|
|