Originally posted by Atma X

---

What does it mean when it says that "something" writes to the H Scroll value in $2005 range from 0 to 256. (what is $2005,... is it an address, and if so, why does the H Scroll value have to be at address $2005?)

---

---

Can you give me some instructions on that to help me get started?

---

---

BTW: The only thing I saw on irc.esper.net was a "Parent Directory" page .

---

Originally posted by HyperHacker

---

and C++... *shudder* If #include and string handling don't get you, the API will.

---

---

Really, though, if you just want to learn any form of ASM, try Z80/Gameboy

---

---

and for general programming, VB6.

---

Originally posted by Disch

---

(sorry HyperHacker... but I feel compelled to intervene whenever I see anyone actually recommending VB).

---

Originally posted by HyperHacker

---

Well sure, C > VB, but which do you think would be easier for someone just learning programming?

---

---

As for what I meant by #include, it just drives me looney having to search through a coupla million header files to find a declaration, then include the entire file, sending my EXE's size skyrocketing with dozens of functions and variables I don't need, instead of just having each function and variable included as they're used.

---

---

Plus, since every compiler uses a different set of library files, one person's code often won't work on another, or even the same compiler.

---

---

Working with strings is just wretched,

---

---

and whether it's the language's fault or not, Windoze's API SUCKS,

---

---

and in VB you don't have to deal with it as much.

---

Originally posted by HyperHacker

---

Still, they need to just delete the whole damn thing and start over.)

---

Originally posted by HyperHacker

---

Filesize? 24K for a VB program that creates a window, or 380K for a C program that does it?

---

---

Just #include <windows.h> sends the filesize skyrocketing.

---

---

It makes more sense to me to just tell it what functions you want,

---

---

True, I love the basics C's syntax, but having to do everything manually can be a pain.

---

---

If I'm going to do it that way, I want to do it with ASM, so that I don't have to deal with stupid limitations and pointers to pointers to integers and all that BS.

---

---

After a few lines of 'someThing->WTF += bhCms(*&&otherThing.cooCoo,*$variable)' I just want to throw up. (Which is another problem, people write such horribly messy code in C, sometimes deliberately. Being able to write everything on one semi-colon-separated line, and crazy things like '#define function1(x) function2(x)' doesn't help. And before you say it, in the real world sometimes you have to edit other peoples' code.)

---

Originally posted by HyperHacker

---

Well, if you find making a window so easy in C, why don't you explain it? I can't make any sense of it. That's really the only reason I still use VB.

---

Originally posted by HyperHacker

---

somefunction:
[some instructions here]
.subfunction:
[more instructions here]
ret

call somefunction.subfunction
Thus skipping some of the instructions in somefunction instead of having to write a duplicate function without them.

somefunction:
[some instructions here]
ret

otherfunction:
[some instructions here]
jp somefunction

Thus going directly from otherfunction to somefunction, which saves an instruction (don't need to do 'ret' after otherfunction) and some stack space (don't need to store the address it came from).

---

  void foo() // somefunction
  {
    //some work part1
    bar();
  }

  void bar() // .subfunction
  {
    //some work part2
  }

  // global variables to simulate registers