thedustbustr

Members
  • Content count

    534
  • Joined

  • Last visited

Community Reputation

191 Neutral

About thedustbustr

  • Rank
    Advanced Member
  1. 1.5hr of coding in their smaller than by bedroom office with 4 desks lol objective was: - develop a mechanism to define a schema and validate a json object against it - coerce data to schema types if possible, in case an int came in as a float or str - develop mechanism to convert between versions of schema I googled an MIT licensed json validator and patched in coercion support. output.txt json_validator.py diff of hacked library
  2. Trying to decide between C4 engine or XNA

    late to the discussion :( We use C4 at work. I've never used XNA but a colleague has. Say you're writing a FPS and you want a real level. You get a bunch of content and import it into your XNA game. Your small little level runs at 5fps. Import that in C4 and it runs at 80 - because C4 is an engine designed with optimizations for entire levels of full high quality content in mind, and you would have to write/debug most of that (math intensive algorithmy stuff) yourself in XNA. If you're writing a small 1-man-month game w/o any heavy game content & high end graphics, XNA will be just fine and might take less time (or it might not). If you're writing a bigger game (or want to learn the skills required to get hired by a studio) pick an engine.
  3. 2D Mouse Picking

    "color picking" ?
  4. Unity why is C++ still being over-used?

    Quote:Original post by Promit I tend to think that there's a substantial subset of members here who are interested in going into professional development, for which C++ experience is an necessary prequisite. many would argue that you will grow to an *expert* C++ programmer faster if you first learn software engineering in a high level language, 'uncontaminated' by low level concepts. this of course fails when you don't care if you are an expert. therein lies the failure of this industry: the absurd skill difference between an expert software engineer and an average software engineer.
  5. Fannie/Freddie Bailout - Maybe I'm just confused

    The point of a democratic republic is electing people more knowledgeable than you to figure out the important decisions. You put hundreds of people, half of whom have ivy degrees, all of whom care about the US to some degree or another, in a room and call their decisions stupid or uninformed. Our politicians aren't all stupid. All of the politicians understand that they are using taxpayer dollars to support private enterprise. If you allow that they are more knowledgeable in economic matters than us, you might conclude that bailing out some private business is believed necessary to support our economy. We all take for granted that we live (so far) in an economic superpower. Americans as a whole enjoy a superior standard of living relative to many other countries. This isn't coincidence - at the highest level, its because our economy is stronger than other countries'. Similarly, we enjoy a safe environment because we are a military superpower (compare to all the eastern developing nations who get invaded every decade, and not just by Americans). It is in all of our incentives to keep it this way. None of us will be happy if we enter a depression. We're recessing to some degree right now - we can all feel it because we don't have nearly as much disposable income as we used to. Like it or not, we are inextricably tied to the big money businesses who contribute most to our economy. Everyone realizes that the financial system is flawed - but you can't just pause it, refactor it into something better, and reset the state to desirable initial conditions, like a computer simulation. We're stuck with this monolithic spaghetti model and duct-tape politics until some visionary politicians come up with a transition model which inspires agile legislation, so we can rapidly adapt to changing conditions. Its well known in software engineering that the cleanest, best encapsulated models have the fewest bugs - sooner or later, our government models will be refactored into an agile system. Or maybe a singularity crisis will deliver an impulse which readjusts the state of the simulation so we can arrive at an agile equilibrium. Maybe it will be me. For the time being, I acknowledge my ignorance. (Ill tack this on to the end. Elco said "What you want is for people who gamble, to be able to lose." I think that sentiment reflects the flawed duct-tape politics i referred to - but even though we hesitate to (as a side effect) reward 'moral hazard' decisions, it is in our greater inventive to quickly curb the depression which these cutthroat decisions are steering us towards, and refactor the system when we have time to think.) [Edited by - thedustbustr on October 6, 2008 8:26:15 PM]
  6. std namespace not found.

    Quoting Zahlman's sig, "As a general rule, if you post in For Beginners and your code contains the word 'char', you have a bug. std::string roxors teh big one one one one." gd thread on string vs char* modern c++ tutorial on gd wiki
  7. On Granting Inalienable Rights to Nature

    thedustbustr's thm: natural law applies to beings who have demonstrated ability to enforce the applicability of natural law to themselves. so far, only humans meet this criteria. presumably, any sentient being would eventually meet it. if a species has successfully defended its right to natural law, darwinistic survival of the fittest applies. once the trees start defending themselves, we may recognize their natural rights. to me, this is the only consistent way to handle this without relying on arbitrary principles. (natural law being, by definition, free of arbitrary principles)
  8. #pragma once vs. include guards

    who cares? #pragma once is harder to mess up, and its supported on the compilers we target. good enough for me. the whole "inclusion guards are more portable" argument worked when i was younger, but in my particular domain, i care lots about ease-of-use and don't care at all about portability.
  9. Writing documentation without focusing on markup

    Use a documentation-generator tool to parse your code for specially formatted comments. this is your API reference. For high level concepts, DocuWiki is perfect. Try markdown as a "natural formatting syntax" - it renders to HTML but doesn't get in the way of human parsing. StackOverflow uses it.
  10. routing stdout to window/console?

    trhis thread on loggers might be of interest, there is some discussion of replacing streambuf's (i.e. redirecting std::cout to somewhere else)
  11. Junior Programmer - Expectations

    Where I work, a junior programmer would never have to be able to pass that quiz. A working knowledge of C++ and decent understanding of OOP is enough. If you can understand Effective C++ (but not necessarily remember it all) you'd do just fine.
  12. brainstorm tool

    I want a private wiki integrated with a tag cloud visualization, such that each tag represented a page, and the weight of the tag is proportional to the length of the page content. If this does not already exist (pretty sure it doesn't), what pieces should I choose to integrate this my self with minimum development time? I don't have time to bother unless it's doable in a weekend (so that's like, an hour for some of you guys). I've looked at WikiHost but it looks like I'm going to need to modify src and host it myself, and integrate with a tag cloud solution, which is fine. I've found TagCloud Maker on freshmeat, which is PHP. I don't really know any web languages, totally willing to learn whatever, but emphasis on minimal time commitment - so please recommend tools for a high level platform if you know of them. If you have brainstorming tools that you use, feel free to chime in. [Edited by - thedustbustr on September 11, 2008 2:52:10 PM]
  13. its happened to me. luckily, i had my project files in source control, so i just reverted everything and continued as normal. good luck.
  14. Best way to employ 'using'

    I've converged on typing out the explicit namespace every time for clarity. Yea, if you see cout, you know what it is. But if you see 'copy' - is it std::copy or is it your method or is it some library? In my own code, I keep my namespace names really short - 2 or 3 characters. I don't nest my own public namespaces unless there is a demonstrated need, it adds too much confusion. when using some spectacularly long nested namespace in boost, I'll put a 'using namespace' at method scope. this means that when I read this code next week I'll have explicit reminder of what namespace I'm in, right there in front of me so I don't have to scroll up to remember. if you're using a nested namespace all over, alias it into a shorter one. 'namespace fs = boost::filesystem;'
  15. i dont understand how this is a problem for trivial conditionals. for complex conditionals, you could factor them all into IfCondition() functions which can be used in a line coverage tool. i really really doubt that you will find a free tool for this.