Code center > Bugs and fixes

DB 2.48.27 crashes on Wine under Mac

<< < (3/4) > >>

Botsareus:
Yes, a while back Numsgil started a port to C++. I was not trilled about the idea at the time mainly because I was working on some reasonably advanced stuff and using vb to do it was easier than learning a new language. I think he got a good chunk of physics and DNA execution ported. Not really sure why he switched over to c# other then to attract new age devs. and start fresh. Something I kinda wanted to ask him actually.

The thing with C++ is that it is not the best language to try new stuff in. I guess that was one of the reasons to use c#.

Honestly, If I knew how much hard time I will be having debugging in vb6 I would have considered a port to something like Java a long time ago. I become aware of the concept of stack tracing about 3 years ago studying for a MCPD exam. I think C++ also has better debugging than vb6 but will need to wait for Numsgil to confirm.

Really, the way I expected everything to go was Numsgil finishing his port to c++ and then me sticking my features in and be done with it. But, I found out on more than one occasion life never turns out the way one expects it to turn out. I digress, I expected to be making real video games for a big time company by now, but in reality all I have is a technical institute certificate that may or may not help me skip some introduction to programming classes in a Uni.

EnderCrypt:
yeah its really ashame that life doesent progress as expected hmm... i wish i had C/++ skills, sadly at the moment i just know webdev/java/lua, nothing fancy really

but yeah, what options for debugging are there in VB6? i mean, i would thought that even a slightly older language would have had some sort of error tracking? is there no way to catch errors and where they occured?

Botsareus:
The error tracking is good and user friendly and all but it only works if you run the project from vb6. Once you compile and distribute the exe all bets are off. Especially with something like db2 where something may go wrong after running it for a very long time and enough possible things that can go wrong it really becomes like rocket science. Once you transfer from a simulation into a real life you really hope it will not end up like the space shuttle program.

EnderCrypt:
hmm... maybe... isnt it possible for you to like... to a test version with lots of console outputs or dialog boxes that apper, with numbers for the [start new] button when you start a new simulation? i dont know how much code there is or if it would be annoying to do, but thats really the only way i know that the error could easily be tracked down? i'd do it myself or even debug the source, if i was able to install VB on my mac

Botsareus:
... Something funky is going on there that has nothing to do with how the start new button works. Maybe you have an im.gset file in the db folder, just guessing. Did you try a clean install and then loading your lastran,set file like I just did from vb6?

Navigation

[0] Message Index

[#] Next page

[*] Previous page