Programming Discussion Thread

**AnyOldName3** · 07-10-2016, 10:04 AM **#621**

I'd recommend Python as a first step to learning to program - it's not great for actually writing programs, but you can learn the basics of how you might without getting bogged down in anything complicated. For a day-to-day language, despite being mostly a Java guy, I'd recommend C#. As I see it, it's Java's younger, prettier, sexier and more intelligent sister. It can do everything Java can do (i.e. be powerful without giving you the opportunity to shoot yourself in the foot), but has nice things like operator overloading, pass-by-reference and a template/generic system that is helpful. It's main disadvantages are because it's a bytecode language, so can end up creating slower programs than C++ (although a good JIT-based runtime can sometimes make it go faster), and also isn't great for interacting directly with hardware. Until something like Go or Rust takes off, you're basically stuck with C++ for that.

**KHg8m3r** · 07-10-2016, 01:25 PM **#622**

Labview is great for interacting with hardware, and is what we use at school for robotics.
It's also very easy to make an interactive GUI with it.

Other than that, it's not a very useful language.

***Shonumi*** · 07-14-2016, 03:42 PM **#623**

Been a while since I posted in this thread. Anyway, been working on the Game Boy's Serial Input/Output, which basically means the Link Cable (though it sets the foundation for GB Printer support). I just implemented a way to sync two instances of the emulator. Some games don't require it, but some games do. Only 1 game I tested doesn't work with GB netplay (Road Rash, it does something weird, needs more debugging).

Anyway, here's a pic of me fighting myself in Pokemon Gold (left) vs. Crystal (right). Given that the opponent was myself, it was a tough battle. Somehow, though, I managed to win: http://i.imgur.com/gmZIofa.jpg

**KHg8m3r** · 07-14-2016, 08:50 PM **#624**

Looks awesome Smile

Also, nice background.

***Shonumi*** · 07-15-2016, 01:14 AM **#625**

Yeah, pretty much as early as I can remember, back when I first started making any real progress on GB emulation, I've always wanted to emulate the Link Cable. You have to realize just how important it is for me to be able to trade Pokemon with myself! Now I can legitimately catch most of the Pokemon without resorting to hacks, cheat codes, or glitches.

So far, it only works on the same computer, but it shouldn't take much to get it working over a network soon.

**KHg8m3r** · 07-15-2016, 01:59 AM **#626**

Would that link cable be able to interface with the Dolphin GC/GBA interface?

07-15-2016, 04:32 AM **#627**

(07-10-2016, 09:35 PM)DolphinGCWii Wrote: I used turbo c++ to learn c++. But it don't show the output message. Any other application for C++?

oof...
Do you mean that cout (or printf) doesn't show up?
Does it show up when the program exits?

If the above description is correct, then your program output is stuck in the buffer, and won't show up because Turbo C++ isn't flushing the buffer. I got the same problem with Eclipse and MinGW. You either have to tweak some setting, or add cout.flush() whenever waiting for user input (or when you want stuff to show up).

Also you should switch to Mingw-w64. It's a newer, more popular, and free and open-source compiler.

***Shonumi*** · 07-15-2016, 03:20 PM **#628**

(07-15-2016, 01:59 AM)KHg8m3r Wrote: Would that link cable be able to interface with the Dolphin GC/GBA interface?

Well, the DMG/GBC link cable is different from the GBA link cable. Serial I/O is different on the GBA. But, once I get around to adding Serial I/O to my GBA core, I don't see why not. That is to say, I've tried to make the DMG/GBC interface relatively straightforward (e.g. functions for sending, receiving, and requesting syncronization), so I can adapt that to fit the GBA

**KHg8m3r** · 07-16-2016, 01:51 AM **#629**

Ok, good luck with that Smile

**DacoTaco** · 07-16-2016, 02:10 AM **#630**

(07-15-2016, 03:20 PM)Shonumi Wrote: Well, the DMG/GBC link cable is different from the GBA link cable. Serial I/O is different on the GBA. But, once I get around to adding Serial I/O to my GBA core, I don't see why not. That is to say, I've tried to make the DMG/GBC interface relatively straightforward (e.g. functions for sending, receiving, and requesting syncronization), so I can adapt that to fit the GBA

just wondering how much these are different?

cause i have a link cable that has the GB© end and GBA connector at both ends of the cable and i can use it just fine with the gameboy player & a gameboy. so somehow they are compatible ?