The Big Programming Thread - Page 179

On October 18 2012 11:57 Craton wrote:
You should really try doing this stuff on your own. It only takes a few minutes to plug in these code snippets and run them. You will learn substantially more from trying than from hearing.

On October 18 2012 09:57 berated- wrote:


Sounds more like you were using vim with a ssh session, and the ssh session failed not the vim edit. You're not using vim locally, are you?

On October 18 2012 20:11 LukeNukeEm wrote:
Somewhat of a broad question (C++11):
what are the differences between

#pragma omp parallel for
for (int i = 0; i < 10; i++)
{
    doSomething(i);
}

and

concurrency::parallel_for(0, 10, [](int i)
{
    doSomething(i);
});

Is there any advantage to either method?

On October 18 2012 22:35 Fyodor wrote:

Well the first one will only work on windows with the microsoft compiler... afaik. I'd use the standard C++11 method for portability/longevity's sake?

Don't know which one is more efficient right now though.

On October 18 2012 20:11 LukeNukeEm wrote:
Somewhat of a broad question (C++11):
what are the differences between

#pragma omp parallel for
for (int i = 0; i < 10; i++)
{
    doSomething(i);
}

and

concurrency::parallel_for(0, 10, [](int i)
{
    doSomething(i);
});

Is there any advantage to either method?

On October 13 2012 07:09 CecilSunkure wrote:

Then do something like this:

do
{
  char input;
  cin >> input;

  // optionally if you include <stdio.h>
  getchar( &input );
} while(input != 'g');

Floats take up 4 bytes of memory. If you don't know what a byte is, try looking it up. A character takes only a single byte. If you are trying to grab a float out of cin (your n variable is a float) it will be looking for something that it can interpret as a float, i.e. a number. You won't be able to convert a float to the character 'g' very easily. This is because the bit format for a float is very different from that of a character.

So, you use cin and extract a single character, which grabs the next 8 bits from the standard in stream (cin). If you aren't familiar with the difference between ' ' and " " in C and C++, then read the spoiler:
+ Show Spoiler +

Edit: I also don't like seeing everyone do "using namespace std;". I guess it's okay if this is only your second class, but really you should be fully understanding what a namespace is, what using means, and what std is. When you write cin you should be manually accessing the std namespace with the :: operator. The using operator clutters your global namespace. I'm just not a fan of using things you don't understand.

do
{
  char input;
  std::cin >> input;

  // optionally if you include <stdio.h>
  getchar( &input );
} while(input != 'g');

#include <cstdlib>
#include <iostream>
#include <stdio.h>

using namespace std;

int main(int argc, char *argv[])
{
    char input[256];
    int n1;
    int sum;
    
    
    cout<<"Enter numbers. Press 'q' to end."<<endl;
    
    do
    {
          gets(input);
          sum=atoi(input);
          n1=n1+sum;
                    
    }
                    
    while (input!='q');
    
    
    cout<<"Okay! The total sum of your numbers is "<<n1<<endl;
    
    
   system("PAUSE");
}

#include <cstdlib>
#include <iostream>

using namespace std;

int main(int argc, char *argv[])
{
    float input;
    float n1;
    
    
    cout<<"Enter numbers. Press 'q' to end."<<endl;
    
    do
    {
          cin>>input;
          
          n1=n1+input;
                    
    }
                    
    while (input!=0);
    
    cout<<"Okay! The total sum of your numbers is "<<n1<<endl;
    
    
   system("PAUSE");
}

On October 18 2012 23:58 FFGenerations wrote:



Thankyou for your reply.

I still dont understand really.

You basically said to use char but I'm not sure what else you said regarding my problem at hand..

So I came to this sort of thing (which doesnt work oc)

+ Show Spoiler +

This isn't school work btw, so go ahead and tell me the solution (relevent to me) if you want..
I thought we might cover it today but we just went straight onto For loops instead.
Honestly I don't think my tutor knows much about indepth coding, in the sense that he wouldn't know how to solve what I'm trying to do..

Thanks again

clean version:
+ Show Spoiler +

#include <cstdlib>
#include <iostream>
#include <stdio.h>

using namespace std;

int main(int argc, char *argv[])
{
    char input[256];
    int n1=0;


    cout<<"Enter numbers. Press 'q' to end."<<endl;

    do
    {
        gets(input);
        n1 += atoi(input);
    }
    while (input[0]!='q');
    cout<<"Okay! The total sum of your numbers is "<<n1<<endl;
}

On October 18 2012 22:36 HomeWorld wrote:
Oh well, since this is a programming thread, hope someone will have a solution for GDI BitBlt using CAPTUREBLT flag (intended for capturing layered windows too) without having mouse pointer hidden/shown every time BitBlt is called. (if this problem gets solved I think it will help a lot "Open Broadcaster Software" - OBSProject)

The problem is that internally MS does a ShowCursor (FALSE) / ShowCursor (TRUE) every time you BitBlt – this creates a Blinking Cursor.

On October 19 2012 17:29 billy5000 wrote:
Hey guys, I've been thinking about getting an android device so I can make a few apps for it (I already have some small ones in mind). However, I'm pretty new to the mobile world and I don't plan on buying a phone. Instead, I found this. Would I be able to make apps for this as well as other android devices? I'm 99% sure that it would (as with all android based devices), but I just need to confirm this before I waste $150.

On October 19 2012 17:36 Blisse wrote:


Please make a few applications, run them on the emulator and see if you actually like the Android environment. It's very easy to just borrow a friend's phone for a couple hours, or call them over to your house to play a bit and use their phone in the meantime, versus spending $150 and then realizing it's not all that you thought it would be. Once you've gotten a taste for it, and actually like it, then you can start thinking about buying a dedicated testing device.

The linked device only supports Android 2.3, so if you're really considering it, start to look into development a bit there first.

On October 19 2012 17:54 billy5000 wrote:


Actually, you somehow persuaded me that I should make web based apps. Somehow lol. I just had a moment of realization why I don't even own an android/ios device in the first place. It's just that 90% of my friends have them, and..yeah, naive.

On October 19 2012 18:07 Blisse wrote:


Well, to be fair, it really doesn't hurt to give development on the emulator a go to see how you feel about it. You may feel that environment has the right feel, or that you really like it, or that you hate it with a passion. Can't tell until you give it a try.

It just seemed like you jumping the gun a bit by spending $150 then flipping a coin on whether you actually like developing on Android. Lots of developers do, and lots of developers don't. It's a preference, and you can't know until you try it out a bit. Not really naive, just a discovery process to see what you like and don't like.

The point is never to reject an idea immediately, but don't jump the gun and focus all your development and learning to the next big, and I use this loosely, "FOTM" when you don't even know if you'll like it. It's never wrong to learn, but you don't want to hurt yourself senselessly.

On October 19 2012 18:20 billy5000 wrote:


I actually have it set up on my eclipse, but the emulator runs unbearably slow on my computer. In addition, I have absolutely no handheld device experience, so there's not a clear distinction of what the consumer wants and does not want.

Anyway, I was mainly curious because I want to finally do something fun and practical after 1 year at my university. It just hit me that I haven't thought about the web. Android/ios apps have that cutesy characteristic, which is probably the reason why I was interested.

On October 19 2012 18:35 Blisse wrote:


Well that's good, then do something fun! It doesn't even need to be practical. It only needs to be something you're interested in; a problem, or to learn, or to do something fun with. And you can have lots of fun doing lots of different things. I know that like, mobile development feels like it's all the rage right now, and that's good, but you can do equally awesome stuff on your desktop as well.

Also, don't worry about what the consumer wants and what you want. If you make something that you really want to use, you can bet there will be people who really want to use it as well. But since you're just starting, just go do whatever the heck you want. If you really want to get into the mobile market, just go for it and work hard, using that $150 as the motivation to push yourself into learning.

It doesn't matter as long as you're interested in it.


If you want to be more conservative, your computer might be slow, but don't let that be the reason you don't look into something you're interested in. If the emulator's slow, I believe there are some workarounds to make it faster. It's apparently even on very good machines. If your machine is just old, then it's a little more complicated.