Borland compilers, by default, tell the FPU to generate floating point exceptions, this can lead to all sorts of problems when linking to libraries that doesn’t expect this behaviour. And that is the case with OpenGL.
The standard advice is to use _control87(MCW_EM, MCW_EM) to disable floating point exceptions.
The above advice does work, but there is a catch, a bug in Borland compilers that resets the floating point control word to _default87 when an exception is thrown (it would be fine if the _default87 value was set correctly by the _control87() call, but that is not the case).
Among other things, the wrong _default87 value reduces the FPU precision and your double precision floating point variables start behaving like single precision ones (but not until your application raises the first exception – arghh!).
From Borland Embarcadero Quality Central:
Workarounds
after any call to _control87 you can use the following line of code to set _default87 to the current control word:
_control87(_control87(0,0),0x1FFF);
Links:
http://qc.embarcadero.com/wc/qcmain.aspx?d=32483
http://qc.embarcadero.com/wc/qcmain.aspx?d=4573
https://forums.embarcadero.com/thread.jspa?threadID=14519
Dear Potential Customer,
If you like Bishop3D enough to go searching for a crack for it then why not just buy it? It’s a lot less hassle and you won’t risk infecting your computer with viruses, spyware and other malware commonly disguised as software cracks.
Bishop3D is developed by a small team. If you like Bishop3D and find it useful, then please pay us for our hard work.
We can even offer you a discount/free license if you colaborate with Bishop3D Wiki, Bishop3D testings, or help us to spread the word about Bishop3D. Just contact us.
Some stuff to keep the search engines happy: crack, cracks, hack, serial numbers, keygen, torrent, warez, licence, license, registration codes, full version download.
I’ve been looking for an automatized way to port the contents of Manual:* parts of Bishop3D Wiki to compressed html help format.
A few days ago I found a light-weight, clean and perfect solution: Connelly Barnes wrote and release to public domain a python script that converts MediaWiki contents to static, traditional, html website. I modified Barne’s script to convert only the pages under Manual:* category in our MediaWiki installation and to write the html help workshop project files based on our Manual:Contents page.
After fixing a few rookie mistakes – I had never written anything in python – I got it working flawlessly. Pretty neat that python thing!
Bishop3D has reached a crucial milestone with its first distribution release.
There is still much room for improvement (and there are plans and will to implement that) but right now a little celebration is deserved (especially if you look at the number of similar initiatives that never made out of the development boxes).
I want to thank everyone who helped with testing suggestions, and criticism (you know who you are) – Thank you very much!
We are starting a new development cycle and essentially everything is open for discussion. If there is anything you would like to see in the future versions or something that you don’t like about the application, feel free to bring it up at the Bishop3D discussion board.
Bishop3D has its first release candidate.
From the first call for alpha testers posted on POV-Ray newsgroups to the conclusion of beta tests, it has been a long and exciting journey.
To everyone involved in the tests: thank you, your criticism, suggestions, feed-back and support have been invaluable.
I stumbled upon this comic at xkcd.
The usual xkcd disclaimer applies:
Warning: this comic occasionally contains strong language (which may be unsuitable for children), unusual humor (which may be unsuitable for adults), and advanced mathematics (which may be unsuitable for liberal-arts majors).
Perhaps this will sensibilize people.
Original kitten image by Clevegrrl available under a Creative Commons Attribution-Share Alike 2.0 Generic license.
I’ve fixed yet another minor bug in Bishop3D today. The bug report was automaticaly generated by EurekaLog (an error logger and reporter tool integrated with Bishop3D) and sent anonymously, after the user’s consent, to our Mantis (a web based bug tracker) installation. Man, it feels great when everything seems to be working nicely integrated.
The bug report contained no information about how to replicate the problem (this part is optionally filled in by the user), but the informations in it made finding and fixing the issue just like shooting fish in a barrel.
Five minutes from getting the bug report to recompiling the unit in order to check the fixes. I think it can’t get easier than that 
In case you are curious, here is the bug itself
The Down button shouldn't be enabled. No good can come from clicking it.
On the Search Paths tab of the text editor Options dialog, if the user selects Import Paths from POVRAI.INI and the search path list is initially empty, then the Down button gets enabled (and it shouldn’t because there is no path selected), clicking it led to a run time exception with the message “Index out of bounds (-1)”.
Starting from version 1.0.3.8 Bishop3D should be fully Windows Vista compatible. I had already fixed the problems with OpenGL rubber band drawing on version 1.0.3.7 and now I’ve sorted out the UAC (user account control) issues.
I’ve just fixed a bug that affected prism objects with cubic_spline interpolation.
The bug prevented the proper detection of spline loops, and therefore its effects are particularly noticeable in prisms with multiple sub-shapes.
Missed spline loop: defective model mesh
Bug fixed: correct model mesh
After fixing the problem I startet to look for some prisms to check the fixes, and remembered that Inkscape can export svg files as POV-Ray prisms.
Flourisch by Nino Barbieri
Flourish exported by Inkscape and Imported into Bishop3D
That is pretty cool but unfortunately it uses only bezier_spline interpolation.
