From: "tyler" <compgeek13@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: c/c++ and linux?
Date: Wed, 4 Jan 2006 22:40:14 -0800 [thread overview]
Message-ID: <004501c611c2$e2b61830$2cc69245@dataplus4puarg> (raw)
Hay list,
I have a question,
I was talking to gabe vega AKA blindtech, and he said he had about 12 years
of linux experience, unfortunately, I wasn't able to talk to him a bit more,
in order to get to know some more about the operating system. Anyway, I have
a question. I am an experienced windows c++ programmer, and have a couple
questions. I am used to using the windows api, and winsock, and etc to
interface to windows and etc, to do what I want. Now, I haven't had any
problem with this, just msdn, and I am usually able to code something up,
with the drawback of coding and testing time, things usually go pretty well
for me. I don't distribute the applications, because I just like to test,
and crash, my own system, and some of them have been fun, and some rather
stupid, admitedly. Anyway, On to my question. How do I use sockets in linux?
I tried to find socket examples, and everyone wants me to use "there library
that they developed." I really can't see what would be wrong with using the
origenal thing, unless I am missing something. Also, does linux have an API?
I know windows has an api, for process management, thread management,
background management, linux woudl have to have stuff for forking and etc.
Any help is appriciated.
Thanks,
Tyler Littlefield.
Check out our website:
http://tysplace.the-leetest.net
check out my blog:
livejournal.com/~tylerrl
[my programs don't have bugs, just randomly added features]
[failure is not an option, it comes bundled with windows!]
reply other threads:[~ UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='004501c611c2$e2b61830$2cc69245@dataplus4puarg' \
--to=compgeek13@gmail.com \
--cc=speakup@braille.uwo.ca \
/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).