Your replies are an example of exactly what I am talking about here regarding support from the Linux community. Look at the huge number of things you got blatantly wrong so far:
1) The initial handling of argc and argv are not done by your application but by the linker. 2) In C, argc and argv are on the stack, ready to be used, but not necessarily in assemblers 3) GTK+ has no influence on the command line until you call gtk_init on it In reality, this is what it actually is: 1) Argc and argv are initially processed only by the OS, and never by the linker or GTK or any compiler until after main() is called. Nothing you can do with the linker, GTK, or the compiler can change that fact. 2) Assemblers don't have their own calling conventions. OSes have their own calling conventions and you pick a compiler with the same calling convention, or you hand program yourself, or your program will never work. 3) In C code, main(*argc,***argv) means the starting point for your program has been called and you can access the command line via argc and argv. In fact, gtk_init(*argc,***argv) will not work if you do not pass it the command line arguments, argc and argv, which you get from main(). You obviously know absolutely nothing about system assembly language programming, yet you are offering advice to people about it as if you were an expert? You shouldn't even be in this forum offering advice on things you know nothing about, so I am not responding to you anymore. You can BS some of the people some of the time, but you can't BS all the people all the time. _______________________________________________ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
