Jump to content

  • Log In with Google      Sign In   
  • Create Account

Banner advertising on our site currently available from just $5!

1. Learn about the promo. 2. Sign up for GDNet+. 3. Set up your advert!


Member Since 18 Aug 2002
Offline Last Active Oct 21 2013 12:01 PM

Posts I've Made

In Topic: Floating Point Constants

02 August 2012 - 03:46 AM

Well then it seems highly unlikely you need to worry about loss of precision when converting from float to double, unless your simple arithmetic involves numbers like 23423.4234234098029384233409583405 Posted Image

Of course, do note that simple decimal expressions like "0.3" have an infinite number of digits in binary fraction form and will suffer additional rounding if coerced to float.

In Topic: Software for at-a-glance overview / organizing of 9001 Projects?

21 June 2012 - 01:41 AM

Nothing out there quite like I want. Rolling my own pile of hacks: http://i.imgur.com/ET1Me.png
Needs more icons, better sorting metric, more accurate metrics in general, better handling of branches.

In Topic: Software for at-a-glance overview / organizing of 9001 Projects?

16 June 2012 - 04:06 AM

Zol on #gamedev suggests some sort of lightweight sourceforgelet stack that you run locally to quickly share local projects (or their information) with others.

In Topic: Sadistic library authors (my rant about Xerces for C++)

31 March 2012 - 01:48 PM

I'd like to remind all of you that we are talking about XML, Xerces, and libraries. Not languages. If this becomes a language thread, I will end it.

Not to question your ultimate authority, but if it happens with the consent of the OP, and with good manners, whats the problem exactly?

A long, sordid history of language flamefests degenerating into complete and utter shite on this forum, as they attract out every lurker who doesn't know what they're talking about but has strong (and wrong) "opinions" and "facts" about programming languages. This derails and prematurely ends thread after thread in the process, either because the concentrated stupid drives away the rest of the participants, or baits them into participating, or gets bad enough that a moderator has to close it.

Premature thread death is seen as bad for some reason, so effort is taken to avoid it.

My point is merely that the typical usability of a library is strongly intertwined with the characteristics of the language it is written in; and that C++ scores low on this metric, in my opinion. Not that crazy a tangent, is it?

Wack's bringing up lists of C#, Java, and C++ "pros/cons". Without reading too closely (as like many members, I've taken to skimming past this stuff when it comes up as it comes up so often) that certainly smells like it's getting/heading toward the rather tangential. And -- lets assume I'm full of shit and it's completely on topic (since I am skimming after all) -- it's still exactly the kind of thing that will attract the wrong sort of people and conversation.

So what can be done? Well, if you're Promit, you can tell the wrong sort to fuck off before they even start, and remind the right sort not to fall into the trap again.

And now you know ™

In Topic: Are dirty coding techniques okay to use?

27 March 2012 - 12:10 AM

Let's say that "_randomString" is the variable that you want to return, but perhaps you have no way of modifiying the "Brute" class to allow you access to this variable.

Even modifying 3rd party headers is preferable to the complete evil that is random address offsets. I don't care if Jesus smacked you with a bible-by-4 and said "thou shalt use this address instead of modifying mine headers" -- I'd still prefer it over this nonsense.

No code is perfect, and practicality takes precedence over trying to be perfect -- but even if you're going to do the wrong thing, don't use that as an excuse to not even try. Asserts, sanity checking, a few comments warning about how you're expecting it to break and why... try to make it so that, when it inevitably breaks, that's okay because the how and why are clear.

Random address offsets aren't going to break cleanly nor clearly. Down that path lies memory corruption, heisenbugs, and crashes 2 hours down the line in a completely unrelated part of your program.