compiler/callfunction

Hurr, getting into the basics of C++ here, and running into issues with calling user defined functions more often that I feel I should. I wrote a mock program to test the issue, and I'm still running into trouble:

#include <iostream>
#include <cmath>
#include <cstdlib>
#include <ctime>
#include <iomanip>

using namespace std;
int randGen ();

int main ()
{
    srand ( time ( 0 ) );
    cout << randGen;
    cin.ignore().get();
    return EXIT_SUCCESS;
}

int randGen ()
{
    srand ( time ( 0 ) );
    return ( 1 + rand ( ) % 10);
}

It compiles, but it tells me "[Warning] the address of `int randGen()', will always evaluate as `true' " and the only thing it outputs is "1" when I want it to output a random number between 1 and 10.

help?

Stop using C++.

Start using Perl.

>>1
Maybe you call the function instead of printing it. And stop using C++.

What's wrong with C++?

>>5
http://dis.4chan.org/read/prog/1289007823/2,6,7

#include <iostream>
#include <cstdlib>
#include <ctime>

using namespace std;
int randGen ();

int main ()
{
    cout << randGen();
    return 0;
}

int randGen ()
{
    srand ( time(NULL) );
    return ( 1 + rand ( ) % 10);
}

>>7
YOU HELPED HIM!

^{no exceptions!}

{code]
#!/usr/bin/env perl
use strict;
use warnings;
               
sub GetRand{
my $num = rand ();
return $num;   
};

my $number = 10 * &GetRand();                          
printf ("%u" , $number );
[/code]

fffffuuuuuBBCODE

>>10-11
IABTR

ONLY SRAND ONCE DAMMIT

I prefer to start with mpiler which is dual to compiler.

"[Warning] the address of `int randGen()', will always evaluate as `true' "
What if you setup your link script to put the function at 0x00000000?

>>7

When I did that it works, but if I try output the value multiple times in a loop, I'd get the same randomly generated number for each time it was called.

lol sepples

>>16
Yeah, that's expected behaviour. Random numbers will do that some times. Because they're random.

>>18
an array of 30 random numbers shouldn't all be the same number. and a rerun of the program will result in a different number than the initial run but all 30 outputs will be the same number.

that's not random, there's some flaw in the way the program is grabbing the numbers.

>>19
Well, see, that's just the thing. By the Law of Truly Large Numbers, if enough people run that program, sooner or later any improbable sequence would have happened. It just so happens you were the lucky one.

>>16
Maybe because you're seeding using time and your processor is too fast. Try hitting your turbo button before executing your code.

Oh, I see! So rand() can only make new numbers so fast.
I added system("sleep 1") to randGen, and it works fine now
thanks, everyone!

>>22
IHBT

>>22
system("sleep 1")
`INHOUSE SOFTWARE WRITTEN BY AN INTERN FOR A SMALL TO MEDIUM SIZED COMPANY' - QUALITY

/prog/ is so helpful.

HELP MY ANUS

I'm actually feeling helpful today. Take out system("sleep 1") and never use that again. Ever. Then move srand ( time(NULL) ); from randGen to the beginning of main.

#define system(...) printf(__VA_ARGS__), exit (255)

or even just

#define system

>>27
That's not being helpful, that's sabotage of our fine efforts.

>>28
#define system(a) assert(!a)

#define system(s) system(s)

>>30
system(0);

<-- check em dubz