OSDev.org

pranavappu007 wrote:I forgot that I had a thread in here

pranavappu007 wrote:I googled about forth and it is as old as C or older. Also, when I look at an example, it is much weirder than languages I've learnt(basically C..). I think it is more used for scientific computing or such, and I've read that it is extensible and therefore not consistent from program to program. Even if I learned it it is less used than C and I don't see it's becoming widespread than C in future.

pranavappu007 wrote:I was thinking about learning Win32 API in C as Windows developer can get more jobs than just C dev. I kinda looked at the basics, it's hard too. But, I think I don't need to use much C++ features if I have to code in CPP. Is it a good idea?

eekee wrote: Uh... it's C on Windows, so if it's not your long-term plan, yeah? I say "not your long-term plan" because Win32 is very old and very bad -- at least the graphics side of it is widely considered very bad. I heard Microsoft have tried to kill it off, but much like x86, demand for compatibility has kept it alive. I imagine there's a few years left in it; time to get practice with C while getting paid. I don't know what the C vs. C++ situation is in that field.

eekee wrote:Just to scare you, there's an image somewhere on the Net with listings of minimal graphical hello world programs in Win32, X Windows (probably Xlib), and Plan 9. The Win32 listing is in a font half the height of the others and is still more than twice the length of the X listing... and people hate X for being too much work! The Plan 9 listing is about 1/5th the length of the X listing. It's a shame there are virtually no Plan 9 jobs.

pranavappu007 wrote: Also I would like to ask, Is there any other method to code for windows except store app and legacy Win32, as you said win32 has only some years left? If all traditional apps are in it, that is not the case..?

iansjack wrote:Choose .NET.

Korona wrote:C and C++ have much more jobs than Rust. (But Rust is still a decent replacement for C)

pranavappu007 wrote:I have college experiences for C++, but I can't exactly figure out how those OOP concepts of C++ map to assembly.

class Cat {
   Cat(int age) : age_(age) {}
   ~Cat() {}
    int GetAge() { return age_; }

    private:
        int age_;
};

typdef struct {
  int age;
} Cat;

Cat* CreateCat(int age) {
  Cat* cat = malloc(sizeof(Cat));
  cat->age = age;
  return cat;
}

void DestroyCat(Cat* cat) {
   free(cat);
}

int GetAgeOfCat(Cat* cat) {
   return cat->age;
}

AndrewAPrice wrote:

Code: Select all

typdef struct {
  int age;
} Cat;

Cat* CreateCat(int age) {
  Cat* cat = malloc(sizeof(Cat));
  cat->age = age;
  return cat;
}

void DestroyCat(Cat* cat) {
   release cat;
}

int GetAgeOfCat(Cat* cat) {
   return cat->age;
}

And implement similar functions (CreateCat, DestroyCat, GetAgeOfCat) in Assembly.

release cat;

free(cat);

PeterX wrote:I think

Code: Select all

release cat;

should be

Code: Select all

free(cat);

AndrewAPrice wrote:You're right. I made an embarrasing mistake!