public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rayne <hjazz6@ymail.com>
To: gcc@gcc.gnu.org
Subject: Difference between Windows and Linux GCC compiler
Date: Fri, 31 Jul 2009 05:06:00 -0000	[thread overview]
Message-ID: <970794.64142.qm@web65309.mail.ac2.yahoo.com> (raw)


Hi all,

I'm interested to know what is the difference in programming using MS Visual C++ on Windows and using the GCC compiler on Linux, i.e. what are some of the things I can do on Visual C++ that won't compile/run on Linux, and vice versa.

For example, I know that Windows uses the LLP64 model, while Linux uses the LP64 model, so the long data type is only 32-bit on Windows but 64-bit on Linux. Also, the windows.h file is only available in Windows, and can't be used on Linux. I've also read that there is also some differences in network programming, since winsock, and especially the underlying ip headers are much different in Windows than Unix/Linux gcc. Is this true?

Thank you. 


      

             reply	other threads:[~2009-07-31  5:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-31  5:06 Rayne [this message]
2009-07-31  5:27 ` Ben Elliston

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=970794.64142.qm@web65309.mail.ac2.yahoo.com \
    --to=hjazz6@ymail.com \
    --cc=gcc@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).