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

[ed boy]

Have it output the time before it starts, and have it output the time at the end.

[Blacken]

What's the best and/or easiest way of figuring out how long a particular section of code spends running in C++ (for optimization purposes)?
I'm using MSVC++ 2008 EE if that helps.

The best way, if you're working in Visual Studio, is to get a full copy of Visual Studio and run it through the profiler--no joke, the VS profiler is the best in the business. Profile-guided optimization is awesome. (GCC can do PGO too, but its profiling tools are a little squishy and more difficult to use, except from within XCode on a Mac.)

The next-best way is to use timing code and measure it in your program, but that's going to involve modifying your code directory. Building a stopwatch class or something is probably the most easily-extricable way.

[alway]

What's the best and/or easiest way of figuring out how long a particular section of code spends running in C++ (for optimization purposes)?
I'm using MSVC++ 2008 EE if that helps.

The best way, if you're working in Visual Studio, is to get a full copy of Visual Studio and run it through the profiler--no joke, the VS profiler is the best in the business. Profile-guided optimization is awesome. (GCC can do PGO too, but its profiling tools are a little squishy and more difficult to use, except from within XCode on a Mac.)

The next-best way is to use timing code and measure it in your program, but that's going to involve modifying your code directory. Building a stopwatch class or something is probably the most easily-extricable way.

Figured as much. Since my university classes don't start until later this month, no free VS'08 for me yet. My code currently uses QueryPerformanceFrequency and QueryPerformanceCounter for FPS, so I'll probably just use that for optimizing as well.

[eerr]

xcode does c++?

[Blacken]

Sure. It's a frontend for the GNU compiler collection--it would be stranger if it didn't support C++.

It also doesn't come even remotely close to NetBeans or Visual Studio, but you can't have everything.

[DrPizza]

What's the best and/or easiest way of figuring out how long a particular section of code spends running in C++ (for optimization purposes)?
I'm using MSVC++ 2008 EE if that helps.

The best way, if you're working in Visual Studio, is to get a full copy of Visual Studio and run it through the profiler--no joke, the VS profiler is the best in the business. Profile-guided optimization is awesome. (GCC can do PGO too, but its profiling tools are a little squishy and more difficult to use, except from within XCode on a Mac.)

The PGO may work well, but VS's profiler is shit compared to the tools available on Mac OS X (for free).

[Siquo]

So... I've got a challenge

I've got a world, made out of cubes. And it looks like crap minecraft. So what I want is to "smooth" it over, at least until you start digging.

Now, interpolating vertices according to the neighbour-blocks is easy, but only works in 2d. As I've got overhangs and caves, that's not going to work. The sides and bottom faces of a cube need "smoothing" as well, and preferably smoother (taking more than just nearest neighbour) than just "ramps" like DF uses (45-degree connections between cubes).

So what I need is a three-dimensional function that can trace smooth lines over discrete points, needs only a few of those points to do so, and is fast. I've come up with tons of ideas that were all bad.

Any ideas?

[Outcast Orange]

Sounds sexy.

[Rose]

marching cubes

look it up

[Siquo]

Awesome, thanks Japa! I'll look into it tonight.

Yes Outcast, I'm doing a Cloudscream Although at only a few lines of code per day, it's coming along pretty slowly. Wait until 2040.

I've got procedural textures and procedural terrain, though. Yeah.

[Outcast Orange]

Very cool.

I'm more interested in your GUI though. Will there be mouse controls? How will the camera work?

[Siquo]

I'm very interested in how that's going to work, as well... 

As with most projects, the boring stuff comes last (read: never). Frankly, I've got no idea how I'm going to do the GUI, but probably use a library from somewhere because it's just a plain bore to design (as in: I started on a technical design, then got bored). You have to make things poppable draggable clickable typeable etc and every event needs to percolate down through layers or not depending on event handlers etc. Making a functional design is already boring (as in, I do that stuff enough at work), making it technically work is just re-inventing the wheel.

[lordnincompoop]

Minor necro, but I have a question on bitshifts. I hope you don't mind.

I'm starting to see a pattern in them. Bitshifting x by y bits is equal to x*2^y, and a bitshift right is x/2^y, right? Or am I completely off my rockers?

Sorry if I'm being ignorant here, as I'm rather new to this stuff.

[ILikePie]

I think so, though I'd be the last person one would look to for programming help. iirc it says something like that in the K&R book.

[Normandy]

Yes. http://en.wikipedia.org/wiki/Bitwise_operation#Bit_shifts.