• Content count

  • Joined

  • Last visited

Community Reputation

145 Neutral

About AndiDog

  • Rank
  1. You might want to try "epydoc". Its tags are very similar to Doxygen, but it works with Python files.
  2. Interval search?

    It's called "binary search" -> O(log n)
  3. mutable and const

    Why is your 'read' function declared const? Just remove it and you won't need 'mutable'.
  4. RC4 (arcfour) question

    The RC4 encryption is used for WEP encryption by WiFi network devices. RC4 is still considered safe with one drawback: You can find the encryption key (e.g. WiFi password) easily by investigating on the first xxxx bytes. So if you drop these bytes, you will improve security. Note that I'm not really into cryptography either, but the above is what I heard about WEP cracking. Look into Wikipedia. The article describes what I said.
  5. hi. im beginning linux game programming...

    For Blender, I recommend the wiki book Blender 3D: Noob to Pro. It's great!
  6. Documenting your code...

    You might want to use Doxygen. It can create HTML output and other formats. Once you learned and configured it, it's very easy to use.
  7. I can only set up Insight as a graphical interface for GDB, but that's not really JIT debugging ;)
  8. I wonder if there's an alternative to Dr. MinGW for debugging GCC-compiled applications on Windows. My problem is that I updated to the experimental GCC 4.3.0 (TDM builds) and it seems to produce unsupported debugging information or whatever. Anyway, sometimes Dr. MinGW crashes itself :D - the window only pops up shortly. It seems like Dr. MinGW isn't developed anymore. And I don't want to use the Microsoft tool Dr. Watson - it doesn't support the debugging symbols either. So now to my question: Are there other free graphical JIT debuggers available?
  9. Quote:Original post by Holland I can't, however, find any good references on how these callbacks work. There's tons of vorbis decoding examples on the internet! I can't believe you didn't find anything... For instance there's the official Vorbis documentation (vorbisfile). There's an example showing the use of ov_open_callbacks. It uses the standard input, but it's pretty similar for files. You only have to provide the callback functions as described here. Your FILE pointer (or whatever object you use to open files...) will be the datasource variable.
  10. You should add them to your project. Don't use the include statement, this isn't usual for source code files (only for headers!).
  11. There's either - a matching source file (.c or .cpp) to the gltools.h, which you have to compile (just add it to the project using the "Project" menu) - a matching already-compiled file (called library, ends with .a or .lib), which you have to link to your EXE file (Project options > Parameters > Add library/object) Hope that helps. My Dev-C++ is in German, but I think you'll find the roughly translated menu points ;)
  12. The wierdest fullscreen problem

    In that case it might help to just reinstall Windows.
  13. The wierdest fullscreen problem

    That sounds really weird... maybe you could try to execute the program on another computer (might be a Windows/DirectX installation or driver problem). Or look at some tutorial code ( If you're code is correct, releasing resources like textures etc. should not give an error!