Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

Control Flow

2 (2.2%)

Arrays, Strings, Pointers, and References

8 (9%)

Functions

4 (4.5%)

Basic object-oriented programming

30 (33.7%)

A bit more advanced OOP (Composition, Operator overloading, Inheritance, Virtual Functions)

18 (20.2%)

Templates

8 (9%)

Other (Explain)

4 (4.5%)

Working with files?  (Streams)

15 (16.9%)

Total Members Voted: 89

[Virex]

Looks nice. I just have one question:

Spoiler (click to show/hide)

[lordnincompoop]

Looks nice. I just have one question:

Spoiler (click to show/hide)

Broken.

Why don't you try to compile it?

What it does is output the title "Robot Rainbow Ostrich Attack" thrice and the prompt once, then wait for input. It then removes end puncuation like periods and the pronoun "I" and places it into an output phrase. It's not that complex.

Just hard to read, I guess.

[Virex]

I gathered as much. I assume you tried to obfuscate it intentionally? Else I should probably slap you for your coding style...

[lordnincompoop]

I don't normally code like that, no. If I did I'd have to slap myself.

I ignored spacing and stuff just to shrink it, and proceeded to obfuscate it just for kicks. I can probs do better but there you go.

[lordnincompoop]

Sorry for the doublepost & mininecro, but would this work?

Code: (C++) [Select]

enum Status
{
UNSCATHED,
SUPERFICIAL,
MINOR_DAMAGE,
MODERATE_DAMAGE,
HEAVY_DAMAGE,
FUNCTION_LOSS,
DEVASTATING,
MISSING
};

enum SpecProperties
{
BLANK,
BRAIN,
BREATHING,
LOADBEARING,
SEEING
};

class BodyPart
{
public:
int nSize; //Use heads as a metric. NOT THE SAME AS CREATURE SIZE
int nToughness;
int nHealth;
int nPainDelta; //How much "Pain" added per stage
int nBloodDelta; //How much blood is lost per turn per stage
int nOxygenDelta; //How much oxygen is lost per turn per stage
bool bEssential; //Essential to life, really.
Status eStatus;
SpecProperties eProperty;
BodyPart(int Size = 1, int Toughness = 1,
int Health = 100, bool Essential = false, SpecProperties Property = BLANK, int PainDelta = 25, int BloodDelta = 25, int OxygenDelta = 0)
{
nSize = Size;
nToughness = Toughness;
nHealth = Health;
bEssential = Essential;
eStatus = UNSCATHED;
eProperty = Property;
nPainDelta = PainDelta;
nBloodDelta = BloodDelta;
nOxygenDelta = OxygenDelta;
};
private:
}

class Humanoid
{
public:
bool bIsAlive;

int nCurrentBlood;

const int nCurrentBlood = 5000;

BodyPart Head(int Size = 1, int Toughness = 10,
int Health = 100, bool Essential = true);

BodyPart Torso(int Size = 6, int Toughness = 60,
int Health = 600, bool Essential = false);

BodyPart UpperlegL(int Size = 2, int Toughness = 20,
int Health = 200, bool Essential = false);
BodyPart UpperlegR(int Size = 2, int Toughness = 20,
int Health = 200, bool Essential = false);

BodyPart LowerlegL(int Size = 2, int Toughness = 20,
int Health = 200, bool Essential = false);
BodyPart LowerlegR(int Size = 2, int Toughness = 20,
int Health = 200, bool Essential = false);

BodyPart FootL(int Size = 1, int Toughness = 10,
int Health = 100, bool Essential = false);
BodyPart FootR(int Size = 1, int Toughness = 10,
int Health = 100, bool Essential = false);

BodyPart HandL(int Size = 1, int Toughness = 10,
int Health = 100, bool Essential = false);
BodyPart HandR(int Size = 1, int Toughness = 10,
int Health = 100, bool Essential = false);

BodyPart UpperarmL(int Size = 2, int Toughness = 20,
int Health = 200, bool Essential = false);
BodyPart UpperarmR(int Size = 2, int Toughness = 20,
int Health = 200, bool Essential = false);

BodyPart LowerarmL(int Size = 1, int Toughness = 10,
int Health = 100, bool Essential = false);
BodyPart LowerarmR(int Size = 1, int Toughness = 10,
int Health = 100, bool Essential = false);

BodyPart Brain(int Size = 1, int Toughness = 0,
int Health = 30, bool Essential = true);
BodyPart Guts(int Size = 4, int Toughness = 20,
int Health = 300, bool Essential = false);
}
Or should I just make a constructor for that?

[SolarShado]

Question:
I've got some programming experience (Java, bash, some perl), and I'm trying to getting into C/C++ (again). So far I've done a little toying with SDL in (I assume pure) C. Should I focus on C, or jump straight into C++? As I understand, C++ is mostly a superset of C.

Contribution:
 - A decent SDL tutorial: http://lazyfoo.net/SDL_tutorials/index.php

So far, I've created this:

Spoiler: Just toying with SDL{,_image,_ttf} (click to show/hide)

Code: [Select]

#include "SDL.h"
#include "SDL_image.h"
#include "SDL_ttf.h"

int main(int argc, char* argv[]) {

if ( SDL_Init(SDL_INIT_AUDIO|SDL_INIT_VIDEO) < 0 ) {
fprintf(stderr, "Unable to init SDL: %s\n", SDL_GetError());
exit(1);
}

{ //init SDL_image
int flags = IMG_INIT_JPG | IMG_INIT_PNG;
int initted = IMG_Init(flags);
if(initted & flags != flags) {
 printf("IMG_Init: Failed to init required jpg and png support!\n");
 printf("IMG_Init: %s\n", IMG_GetError());
}
}

if(TTF_Init() == -1) {
 printf("Couldn't init SDL_ttf!");
}


SDL_WM_SetCaption("SDL Test",NULL);
SDL_Surface *mainWin = SDL_SetVideoMode(800,600,0,SDL_HWSURFACE);

SDL_Surface *img1 = IMG_Load("/home/adrian/wallpaper/linux-tan.jpg");
SDL_Rect img_src = {140,75,mainWin->w,mainWin->h};

TTF_Font *font = TTF_OpenFont("/usr/share/fonts/TTF/LinBiolinum_It.ttf", 32);
SDL_Color txtCol = { 50, 50, 50 };
SDL_Surface *text = TTF_RenderText_Blended(font, "Linux-tan", txtCol);


SDL_Rect txtPos = {50,90,0,0};
int die = 0;
int cur_x = 0, cur_y = 0;
int sq_h = 50, sq_w = 50, sq_x = 25, sq_y = 25;
SDL_Event evt;

SDL_Rect fullScreen = {0,0,mainWin->w,mainWin->h};

SDL_Rect undermouse = {0,0,50,50};

if(SDL_InitSubSystem(SDL_INIT_JOYSTICK) == -1)
printf("Couldn't init joystick subsys.\n");

printf("Num joysticks %d\n", SDL_NumJoysticks());
if(SDL_NumJoysticks() > 0 && SDL_JoystickEventState(SDL_ENABLE) == SDL_ENABLE)
printf("Joystick events enabled\n");
else
printf("Joystick events not enabled\n");

SDL_Joystick *js0 = SDL_JoystickOpen(0);
if(js0 != NULL)
printf("js0: Axes(%d) Balls(%d) Buttons(%d) Hats(%d)\n",
SDL_JoystickNumAxes(js0), SDL_JoystickNumBalls(js0),
SDL_JoystickNumButtons(js0), SDL_JoystickNumHats(js0));


while(!die) {
if(SDL_PollEvent(&evt)) {
if(evt.type == SDL_QUIT) {
die = 1;
}
else if(evt.type == SDL_JOYAXISMOTION) {
        printf("JoyAxisEvent (%d,%d)\n", evt.jaxis.axis, evt.jaxis.value);
}
else if(evt.type == SDL_JOYBALLMOTION) printf("JoyBallEvent\n");
else if(evt.type == SDL_JOYBUTTONUP) printf("JoyButtonEvent (up)\n");
else if(evt.type == SDL_JOYBUTTONDOWN) printf("JoyButtonEvent (down)\n");
else if(evt.type == SDL_JOYHATMOTION) printf("JoyHatEvent\n");
else if(evt.type == SDL_KEYDOWN) {
if(evt.key.keysym.sym == SDLK_q) {
die = 1;
}
if(evt.key.keysym.sym == SDLK_UP) {
sq_h += 2;
sq_y = sq_h / 2;
}
if(evt.key.keysym.sym == SDLK_DOWN) {
sq_h -= 2;
sq_y = sq_h / 2;
}
if(evt.key.keysym.sym == SDLK_RIGHT) {
sq_w += 2;
sq_x = sq_w / 2;
}
if(evt.key.keysym.sym == SDLK_LEFT) {
sq_w -= 2;
sq_x = sq_w / 2;
}
}
else if(evt.type == SDL_MOUSEMOTION) {
cur_x = evt.motion.x;
cur_y = evt.motion.y;
}
undermouse.x = cur_x - sq_x;
undermouse.y = cur_y - sq_y;
undermouse.w = sq_w;
undermouse.h = sq_h;
}

SDL_FillRect(mainWin, &fullScreen, SDL_MapRGB(mainWin->format, 0,0,0));

SDL_BlitSurface(img1, &img_src, mainWin, NULL);

SDL_FillRect(mainWin, &undermouse, SDL_MapRGB(mainWin->format, 255,255,255));

SDL_BlitSurface(text, NULL, mainWin, &txtPos);

if( SDL_Flip(mainWin) != 0 )
printf("problem displaying screen...");
// SDL_Delay(20);
}

SDL_Quit();

}


The main thing that's new for me here is building my own event loop.

(I'm working on Arch Linux mostly, using GCC 4.5.2.)

EDIT: discussion's moved waaay on, so I'm not posting an actual follow-up, but I've decided to focus on C for now.

[qwertyuiopas]

Different people will give different answers for "C or C++". Mainly whether C++ adds great new features, or unnessecary bloats (different names and opinions on the same features).

In my opinion, I feel that it falls more into the bloats category (with exceptions and operator overloading, code suddenly jumping elsewhere without informing the reader is just too easy, or worse, the reccomended thing to do), butit should be up to the individual to decide their opinion, and thus if they use one or the other.

[Shades]

I would recommend C++ over C for pretty much the same reasons as qwertyuiopas doesn't like it (exceptions and overloading. code jumps that aren't exception states are a bad idea, of course you can do that in c as well)

I'd also say the more languages you know the better so there is no reason not to learn C++

[Blank Expression]

In my opinion, I feel that it falls more into the bloats category (with exceptions and operator overloading, code suddenly jumping elsewhere without informing the reader is just too easy, or worse, the reccomended thing to do), butit should be up to the individual to decide their opinion, and thus if they use one or the other.

Your standard library already includes functions that "jump elsewhere" when invoking operators. Allowing a developer to overload it for the purpose of adding together vectors, for example, in a completely and utterly straightforward manner that is completely in line with standard mathematics, increases readability and understanding of code flow.

C++ includes exceptions because exceptional conditions exist. Error codes are a poor substitute and most uneducated and unskilled programmers--i.e., the majority of people reading this thread--will not religiously check them. It is the height of irresponsibility to advocate that people make choices that result in less safe code.

This may be your "opinion," but opinions can be judged on merit, and this one lacks merit. If overloaded operators and exceptions result in you being confused by your own code flow, you should not be writing code.




It's clearly evident that the overwhelming majority of people posting in this thread should be using neither C nor C++ to begin with, but something considerably less unsafe. (The person--Supermikhail, I think it was--saying that they use int16 instead of int32 because of "my OCD" is a perfect example of this, as allocating an int16 in modern desktop C/C++ actually allocates 4 bytes; the request to memory returns those 4 bytes and the top bits are masked away. Your tools have been developed over decades by people who are in all likelihood smarter than you and are vastly better programmers than you. Understand their decisions before you do things that intentionally act contrary to established wisdom.)

[lordnincompoop]

I assume you are a professional/experienced programmer then, or at least knowledgeable enough to talk about this?

And if you consider C/C++ too unsafe, what would you recommend, then?

Oh, and welcome to Bay12, Blank Expression.

[Blank Expression]

I assume you are a professional/experienced programmer then, or at least knowledgeable enough to talk about this?

I have just under eight years of professional experience. I have been programming as a hobbyist for fifteen years.

And if you consider c/C++ too unsafe, what would you recommend, then?

The short answer is "nearly anything else." Python, C#, Java, whatever. The problem lies in the thin abstraction layer of C/C++; C++ attempts to rectify this by including some aspects of more modern programming languages (exceptions, for example). The Boost library attempts to go further (see Boost::Bind, and some of the Boost stuff pulled into TR1). But it is a poor facsimile.

I recommend C# and Java because I find a purely object-oriented approach to be more pedagogically sound than something like Python, where it is bolted on in, my opinion, a bit sloppily, but for a novice, Python is leaps and bounds both safer and saner than C or C++. The folks at GDNet tend to espouse a similar viewpoint, for similar reasons.

Oh, and welcome to Bay12, Blank Expression.

Thank you.

[Shades]

I have just under eight years of professional experience. I have been programming as a hobbyist for fifteen years.

A better look at your experience would probably be how many languages you know well enough to consider yourself competent in. I know enough developers with X years of experience who have just being doing the same thing over and over so could also have been classed as X months of experience. Not saying you are just that I've never found time to be a good indicator among co-workers.

That fact your a hobbyist as well is probably more important from an has actually bothered to learn stuff point of view of course. There appear to be a large number of developers on this forum, must be something about DF that attracts them

[Blank Expression]

A better look at your experience would probably be how many languages you know well enough to consider yourself competent in. I know enough developers with X years of experience who have just being doing the same thing over and over so could also have been classed as X months of experience. Not saying you are just that I've never found time to be a good indicator among co-workers.

My experience should be self-evident from that I am demonstrating a knowledge of what I'm actually talking about, but sure. I can write production-quality code in C, C++, C#, Java, Scala, Groovy, Scheme, Lisp, Visual Basic 4/5/6, VB.net, PHP, Python, Ruby, tcsh, bash, and I have a decent grasp of SQL.

I have worked in a contractor role for Google, have successfully run a consulting business, my name is in the commit logs of a few well-known open source projects, and I currently work for a company whose web application is in the top 300 Alexa rankings worldwide.


This has nothing to do with my point that C and C++ are thin abstractions that are poor starting places for people to learn how to write code, but if the argument from authority is what you want...

[Shades]

This has nothing to do with my point that C and C++ are thin abstractions that are poor starting places for people to learn how to write code, but if the argument from authority is what you want...

It's not what I want but I was querying your initial assertion, and I'd disagree that c++ is any poorer a starting place from c#, probably both python and java and cleaner models for learning though.

[Blank Expression]

This has nothing to do with my point that C and C++ are thin abstractions that are poor starting places for people to learn how to write code, but if the argument from authority is what you want...

It's not what I want but I was querying your initial assertion, and I'd disagree that c++ is any poorer a starting place from c#, probably both python and java and cleaner models for learning though.

You will be very hard pressed to substantiate this. C++ has an antiquated memory model, requires the use of brutal hacks like the *_ptr classes from Boost, and nearly demands leaky abstraction via friend, MI, and other methods of tangling the class hierarchy. Languages on the .NET framework, by and large, lack these problems. As well, I find it very interesting that you make the curiously irrational claim that C# is not a cleaner model, but Java is. You are aware, I hope, of the similarities between the two (damned near identical in most aspects that matter to a novice)?

In addition, regardless of what C++ toolchain you deal with, you'll encounter similarly user-hostile software. The same can't be said of Visual Studio--whatever your personal preference in the IDE holy war, it's incredibly difficult to assert that it isn't both fantastic and very, very popular.