HOLY FUUUUUUUUCK POINTERS
1
Name:
Anonymous
2011-01-24 3:15
why should I return a structure pointer rather than the structure itself
2
Name:
Anonymous
2011-01-24 3:29
• it's smaller
• maybe you want to modify it
• what is with your title this is simple stuff
3
Name:
Anonymous
2011-01-24 5:22
>>1
Because passing around large structures on the stack is
GAY AS FUCK .
Are you malloc()ing a new structure for the person and returning? If so an alternative method is to have them pass in a pointer to that structure then you can modify the structures contents to your heart's content, and it will be modified for the caller too.
4
Name:
Anonymous
2011-01-24 5:37
i like to stack books in my garage
5
Name:
Anonymous
2011-01-24 5:47
6
Name:
Anonymous
2011-01-24 6:14
>>2,3
it's smaller
passing around large structures on the stack
I'm on a 64-bit architecture, you insensitive clods!
7
Name:
Anonymous
2011-01-24 7:21
>>6
So? All the useful programs are only available in 32-bit multilibs anyway.
8
Name:
Anonymous
2011-01-24 7:27
>>6
By passing pointers to structures, you economize size and time, and you can implement abstract data types.
9
Name:
Anonymous
2011-01-24 7:28
>>1
Because you touch yourself, ahh fuck it. Let's stop here.
10
Name:
Anonymous
2011-01-24 10:25
TOUCH MY ANUS
11
Name:
Anonymous
2011-01-24 10:30
>>10
$ touch ">>10- san anus"
$
12
Name:
Anonymous
2011-01-24 11:28
Pointerashi - When The Segfaults Cry
13
Name:
Anonymous
2011-01-24 11:35
ポインターのなく頃に
14
Name:
Anonymous
2011-01-24 17:58
bool EXPERTPROGRAMMERFUNCTION(yourshittystruct* pStruct,int somegayflag);
that's how your function signature should look like.
any other way means you are a ''faggot''
15
Name:
Anonymous
2011-01-24 18:49
>>14
back to kindergarten please
16
Name:
Anonymous
2011-01-24 21:01
17
Name:
Anonymous
2011-01-24 21:24
18
Name:
Anonymous
2011-01-24 22:07
>>14
static volatile long long int Expert_Programmer_Function (struct yourshittystruct*,int);
19
Name:
Anonymous
2011-01-24 23:17
[code] static abstract interface long long double Expert_Enterprise_Programmer_Function (struct* pShit, bool, null, null, null, null, null);
20
Name:
Anonymous
2011-01-24 23:20
static abstract virtual interface long long double Expert_Enterprise_Programmer_Function (struct* pShit, bool);
21
Name:
Anonymous
2011-01-24 23:21
[/code] [/GRUNNUR]
22
Name:
Anonymous
2011-01-25 0:39
[code] static abstract virtual interface long long double Expert_Enterprise_Programmer_Function (struct* pShit, bool, NullPtr* pleaseNullThis, NullPtr* pleaseNullThisAlso, NullPtr* andThis, NullPtr* andThisOneToo, NullPtr* dittoPlease, NullPtr* yepYouWillWantToNullThisAlso, DelegatePtrLong* youWillBeTemptedToUseThisButItWillCrashIfYouDo_Probably);
23
Name:
Anonymous
2011-01-25 0:45
>>22
static abstract virtual interface long long double Expert_Enterprise_Programmer_Function (struct* pShit, bool, NullPtr* pleaseNullThis, NullPtr* pleaseNullThisAlso, NullPtr* andThis, NullPtr* andThisOneToo, NullPtr* dittoPlease, NullPtr* yepYouWillWantToNullThisAlso, DelegatePtrLong* youWillBeTemptedToUseThisButItWillCrashIfYouDo_Probably);
24
Name:
>>22
2011-01-25 1:41
>>23
Thanks, I needed that.
25
Name:
Anonymous
2011-01-25 14:08
static abstract virtual final interface protected unsigned long long int ExpertEnterpriseProgrammerFunction (struct* pShit, bool, NullPtr* pleaseNullThis, NullPtr* pleaseNullThisAlso, NullPtr* andThis, NullPtr* andThisOneToo, NullPtr* dittoPlease, NullPtr* yepYouWillWantToNullThisAlso, DelegatePtrLong* youWillBeTemptedToUseThisButItWillCrashIfYouDo_Probably);
26
Name:
Anonymous
2011-01-25 17:13
27
Name:
Anonymous
2011-01-25 18:24
>>22,23,25
By the way, what's going to happen to that
bool without a variable name?
28
Name:
Anonymous
2011-01-25 18:27
>>27
It'll get named in the definition, duh.
29
Name:
Anonymous
2011-01-25 19:06
>>28
That's a disappointing answer.
Also, thank you for reminding me that some people don't fill that in.
30
Name:
Anonymous
2011-01-25 19:18
31
Name:
Anonymous
2011-01-26 2:40
>>29
I was thinking about something along these lines lately. Headers and structs make up C's strongest feature: a very mild form of self documentation. Working with dynamic languages too often involves looking at code where declarations would have been easier to track down.
32
Name:
Anonymous
2011-01-26 5:11
25 GET
33
Name:
Anonymous
2011-01-26 6:12
check my dubs ^__^
34
Name:
Anonymous
2011-01-26 10:09
chunk my bacon ^__^
35
Name:
Anonymous
2011-01-26 10:56
hax my anus ^__^
36
Name:
Anonymous
2011-01-26 11:43
*grabs dick* ^___^
37
Name:
Anonymous
2011-01-26 14:21
*grabs ^___^* ^___^
38
Name:
Anonymous
2011-01-26 14:26
*^___^s dicks* grab
39
Name:
Anonymous
2011-01-26 22:55
im so ronery... v___v
40
Name:
Anonymous
2011-01-27 1:17
*dicks* "grab" __^__
Newer Posts