Newgrounds.com — Everything, By Everyone.

nice but can you answer my question (last post on page 9).
whoo im definetly not ready for Win32 yet lol.

You ordinarely declare that shit like this:

char stuff[80];

But when using that with stuff like cin>> it makes your program exploitable via Stack Buffer Overflow, which are lame.

At 3/7/05 08:50 PM, RegExp wrote: char stuff[80];

So, would that line declare a varialble that can hold up to 80 characters?

At 3/8/05 08:44 PM, Love_Daddy wrote:

At 3/7/05 08:50 PM, RegExp wrote: char stuff[80];

So, would that line declare a varialble that can hold up to 80 characters?

Seventy-nine technically, because in C and C++ all strings are NULL terminated via \0 so the last space in the array is reserved.

At 3/8/05 08:48 PM, RegExp wrote:

At 3/8/05 08:44 PM, Love_Daddy wrote:

At 3/7/05 08:50 PM, RegExp wrote: char stuff[80];

So, would that line declare a varialble that can hold up to 80 characters?

Seventy-nine technically, because in C and C++ all strings are NULL terminated via \0 so the last space in the array is reserved.

umm ok but what happens if you don't know how long the string will be. This is one of the reasons i like VB more C++.(In this case anyway.) Is there like a trim function like in VB or something. ARG, Dim blarg as string is so much easier.

For all the wenches too lazy to make a c-string, there is a class in the standard library, std::string, which supports all of the nice operations (like infix plus for concat), and dynamically allocates data as needed. In short, you can do:
std::string bleh = "bleh";
std::string arr = "arr";
std::string final = bleh + arr;
printf("%s", final.c_str());
// Output is: "bleharr"
You have to use the c_str() method, when printing using a function like printf or cout, however, because printf and cout print out C-STRINGS, not std::strings. You also have to #include<string> (With no .h).
In general, though, if you allocate a nice big buffer, then it shouldn't be any problem in a game. If you THINK that your string is going to be, like, 90 characters long, make a 128 character string, and you should be fine. And always use multiples of powers of two, just because.

hmmm that might be fine for a couple varablies but wouldn't that slow down your program if you have a bunch of those over declared varaibles. Or would it not really affect the ovaral program? Lol, sorry about all the questions people.

At 3/8/05 08:51 PM, Love_Daddy wrote:

At 3/8/05 08:48 PM, RegExp wrote:

At 3/8/05 08:44 PM, Love_Daddy wrote:

At 3/7/05 08:50 PM, RegExp wrote: char stuff[80];

So, would that line declare a varialble that can hold up to 80 characters?

Seventy-nine technically, because in C and C++ all strings are NULL terminated via \0 so the last space in the array is reserved.

umm ok but what happens if you don't know how long the string will be. This is one of the reasons i like VB more C++.(In this case anyway.) Is there like a trim function like in VB or something. ARG, Dim blarg as string is so much easier.

If you don't know how long a string is going to be, you can either:

A. Make it longer, and just prevent the inevitable Stack Buffer Overflow that will occur unless initiating program Canary stacks or NX stacks.
B. Dynamically allocate enough memory for that, and open yourself up to Heap overflows, which aren't lame like Stack overflows.

i tried plaing around with some dynamic allocating but it ddin't really work. My code was something along the lines of:

#include <iostream.h>

//.........

Dynamic Memory Allocation is frusterating, in all languages, but it's worth learning. It's very easy once you figure it out.

Plus you figure out tons of new things like how to cause system faults all over the place because of DMA raddling out of control.

Lol, dude your the biggest hacker on this forum since JesusCyborg.

At 3/8/05 09:46 PM, Love_Daddy wrote: Lol, dude your the biggest hacker on this forum since JesusCyborg.

I try. But JC knows about eleventy-billion more things than I do.
Also, just for fun, I made this program based on something I read:

#include <stdio.h>
#include <malloc.h>
#define OVERFLOW 8
#define BUFSIZE 16

int main() {
char *buf1 = (char *)malloc(BUFSIZE),*buf2= (char *)malloc(BUFSIZE);
memset(buf2,'A',BUFSIZE-1);
printf("Before overflow: %s",buf2);
memset(buf1,'B',BUFSIZE+OVERFLOW);
printf("After overflow: %s",buf2);
getchar();
return 0;
}

If anybody can guess what it does, say so, if you have no idea what'll happen, stick it in your compiler and compile it (be sure it's a .c file, dunno 'bout you guys, but C programs compile much faster than C++ files for me)

#include <iostream.h>

}

lol, right when you think your making progress in a language you have to go back to "hello World". Well at least i can get text to work now lol. I'll try posting a dynamic allocating text thing in a couple of minutes if i can figure that out.

lol well hear it is but it doesn't work.(but what else is new.) lol. Who wants to fix this......

#include <iostream.h>

}

That isn't dynamic memory allocation. Sorry, try again. :(

Or just look up how to do DMA in C++, because I only know how to do it in C.

At 3/9/05 10:53 PM, RegExp wrote: That isn't dynamic memory allocation. Sorry, try again. :(

Or just look up how to do DMA in C++, because I only know how to do it in C.

ok lol i g2g sleep now but i might try something tommorow.(i put your prog on my site btw)(im not sure if you knew lol)(random)(must stop writing in brackets)(!)

Well here is a little something i made just now. Its a Russian Roulette version of Black Jack. Im gonna upload it onto my site soon in case you want to download it and give it a wirl. Enjoy and feel free to correct any syntax or whatever you can find.176 lines of code just in case anyone cares.

#include <iostream.h>
#include <stdlib.h>

}
return shot;
}

In terms of Dynamic Memory Allocation for C++, you essentially just replace malloc with the new keyword. Just remember that you have to delete memory, and that when deleting arrays you have to do delete[].

char *PointerToMemory;
PointerToMemory = new char;
// Do something
delete PointerToMemory;

char *PointerToArray;
int LengthOfArrayThatCanChange = 100;
PointerToArray = new char[LengthOfArrayThatCanChange];
// Do something
delete[] PointerToArray;

At 3/8/05 10:05 PM, RegExp wrote:

At 3/8/05 09:46 PM, Love_Daddy wrote: Lol, dude your the biggest hacker on this forum since JesusCyborg.

I try. But JC knows about eleventy-billion more things than I do.
Also, just for fun, I made this program based on something I read:

#include <stdio.h>
#include <malloc.h>
#define OVERFLOW 8
#define BUFSIZE 16

int main() {
char *buf1 = (char *)malloc(BUFSIZE),*buf2= (char *)malloc(BUFSIZE);
memset(buf2,'A',BUFSIZE-1);
printf("Before overflow: %s",buf2);
memset(buf1,'B',BUFSIZE+OVERFLOW);
printf("After overflow: %s",buf2);
getchar();
return 0;
}

If anybody can guess what it does, say so, if you have no idea what'll happen, stick it in your compiler and compile it (be sure it's a .c file, dunno 'bout you guys, but C programs compile much faster than C++ files for me)

You will most likely overwrite buf2 when memsetting buf1 to 'B', because buf2 preceedes buf1, so buf2 will be 'BBBBBBBBAAAAAAAA'.

C programs compile faster because it is easier to translate.

Bingo. Heap overflows are sex.

#include "stdafx.h"
#include "mousehook.h"
#include "nat$interface.h" //defines WM_TTI_GIVE_IT_UP

//because a class routine apparently can't be a callback, define global pointer to the class that a non-class
//callback can in turn call

LRESULT CALLBACK gCheckMousePosition(int nCode, WPARAM wParam, LPARAM lParam);
CMouseHook *pMouseHook = NULL;

//
//More shenanigans - these wrapper routines exist so that sp4gl doesn't have to know about the dll, and
//if the dll is nowhere to be found, for some reason, sp4gl can go on its merry way, just without the
//"keep-the-focus" feature
//

#ifdef _WINDLL
__declspec (dllexport)
#endif
CMouseHook *TTI_CreateMouseHook(CWnd *pWnd)
{
pMouseHook = new CMouseHook();
pMouseHook->Initialize(pWnd);
return pMouseHook;
}

#ifdef _WINDLL
__declspec (dllexport)
#endif
void TTI_DestroyMouseHook(CMouseHook *pHook)
{
delete pHook;
}

CMouseHook::CMouseHook()
{
m_pHookProcOld = NULL;
m_pHookee = NULL;
}

void CMouseHook::Initialize(CWnd *pWnd)
{
m_pHookee = pWnd; //keep track of the hooked window
int status;
HMODULE hMod = GetModuleHandle("sp4util.dll");
m_pHookProcOld = SetWindowsHookEx(WH_MOUSE_LL, (HOOKPROC)gCheckMousePosition, hMod, NULL);
if (m_pHookProcOld == NULL)
status = GetLastError();
}

CMouseHook::~CMouseHook()
{
if (m_pHookProcOld != NULL)
UnhookWindowsHookEx(m_pHookProcOld);
}

LRESULT CALLBACK gCheckMousePosition(int nCode, WPARAM wParam, LPARAM lParam)
{
return pMouseHook->CheckMousePosition(nCode, wParam, lParam);
}

#define click ((MOUSEHOOKSTRUCT *)lParam)->pt
//
//the hwnd member of the MOUSEHOOKSTRUCT is supposed to have the hwnd of the window we're clicking on,
//but it's always 0! So we're using click coordinates instead
//
LRESULT CMouseHook::CheckMousePosition(int nCode, WPARAM wParam, LPARAM lParam)
{
if (nCode >= 0 && nCode != HC_NOREMOVE && //user clicked somewhere
(wParam == WM_LBUTTONDOWN || wParam == WM_LBUTTONDBLCLK))
{
RECT rc;
m_pHookee->GetWindowRect(&rc); //in our window?
if (!(click.x >= rc.left && click.x <= rc.right && click.y >= rc.top && click.y <= rc.bottom))
::PostMessage(m_pHookee->m_hWnd, WM_TTI_GIVE_IT_UP, 0, 0);//no! so give up the focus
}
return CallNextHookEx(NULL, nCode, wParam, lParam);
} // CheckMousePosition

Hooks are awsome :). On a related note, I once created a WH_GETMESSAGE hook (which monitors all system messages, sent from anywhere, to anywhere) in one of my apps. I didn't think that it was working though, so in a move of desparation, I made it so that it popped up a message box (That said "Arr") EVERY time a message was sent. You can imagine the chaos.
But -- NG BBS seriously needs a [code] tag or something along those lines, because, as code gets more complex, it gets exceedingly harder to read without formatting and syntax highlighting.

At 3/17/05 07:48 PM, misterPhyrePhox wrote:

But -- NG BBS seriously needs a [code] tag or something along those lines, because, as code gets more complex, it gets exceedingly harder to read without formatting and syntax highlighting.

not a bad idea. I just always bold my code. It makes it a lot easier to read when thiers lots of code.

At 3/17/05 07:48 PM, misterPhyrePhox wrote: Hooks are awsome :). On a related note, I once created a WH_GETMESSAGE hook (which monitors all system messages, sent from anywhere, to anywhere) in one of my apps. I didn't think that it was working though, so in a move of desparation, I made it so that it popped up a message box (That said "Arr") EVERY time a message was sent. You can imagine the chaos.
But -- NG BBS seriously needs a [code] tag or something along those lines, because, as code gets more complex, it gets exceedingly harder to read without formatting and syntax highlighting.

I still haven't figured out hooks. :(
Hell, I still haven't even figured out enough to code DLL files.

I'm so un-1337.

I'm stuck on trying to take the square root of a floating decimal number. The way I tried to do it my compiler got mad if I didn't do it a certain way and even then it never worked.

OK guys i need some help. I made a NG experaince calculator and i compiles but on runtime when it says "press enter to get your result" it will close. When i went to debug the thing i get an error ("unhandled exeption in expcalc.exe......Access violation") on the first line in the getdays() function. Well heres the code someone please help me out thanks.

#include <iostream.h>

return 0;
}

@Love_Daddy: You have two DIFFERENT instances of userstat. One is the LOCAL variable ustat in the function main, and one is the LOCAL variable ustat (same name) in the function getdays. You need to make ustat a GLOBAL variable (or you could pass it to getdays, but whatever), by declaring it outside of the main function.
When you make the local variable ustat in getdays, you don't initialize it -- and so, the values in ustat are all screwed up. When you try to access reqs[ustat.lvwanted], ustat.lvwanted, remember, isn't initialized. Chances are, ustat.lvwanted is some random, random value like 11092843 (just as an example), so you try to access reqs[11092843], which is 11092843 * sizeof(userstats) bytes away from reqs, and it is probably some wierd system memory, which gives you an error when you try to access it.
I think I muddled up the explanation, though...

thanx dude. I fixed the problem by removing the function because it really wasn't needed. I finished the code and im going to make a topic on it in a sec. You can download it and betatest it if you wish.

maybe explaining WHAT the code means would help......

#include <iostream> a # is required by all include statements, the include statement will use the file in the brackets after it (that comes with the compiler) whereas iostream is for input and output basics like saying cout

using namespace std; not required in most compilers

int main(); this starts our program, all C++ programs need a starting function

{ a opening and closing brace is required for every function
cout << "Hello World"; cout basicallly prints to the screen some sort of data, you have to have opening and closing "'s if you want it to print something, and all lines of code usually end in ;
cin.get(); this makes it so when the user types something and hits enter the program closes, without it or system("pause"); you would see the window for about a millisecond

return 0; this basically ends the code
}

and thats a rundown ( a crappy rundown) of the basic hello world program

(i feel so smart) lol