Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt
--------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
Hope it helps a bit ...
Chris
--
----------------------------------------+----------------------------------
Consultancy Services, Programming, | Phone (24h): +27 82 445-3804
Shareware, Freeware and PD Software | Snail Mail: P.O.Box 2485
PROGRESS, Linux, SCO, Windows | Edenvale 1610, South Africa
Strictly: Jeans, Sneakers, Non-Smoking | URL: http://www.eurassi.co.za/
----------------------------------------+----------------------------------
Trying to move from Microsoft C to GNU compiler is proving a little
more akward than I anticipated.. certain functions such as getche()
do not work are not available by the same name under GNU GCC. So, I
would sincerely appreciate getting information 1) about the
functions in GNU GCC/ G++ and two about any books or online docs
that would have info about C programming under Linux.
The question is simply wrong! First of all the things you asked about
extensions of GCC has nothing to do with functions like getche(). The
later come with the C Library. If dumb system like MSDOG don't have a
system C Library it is their fault.
Second the question correctly should be: which extension does
*Microsoft* built in their C Library which prevents we from running on
any other system. GNU/Linux follows the common standards (i.e. ANSI
and POSIX) while Microsoft follows Microsoft standards.
Don't blame the rest of the world for the bullsh*t this M$ concern
produces.
-- Uli
________---------------------------------------------------------------
\ / Ulrich Drepper / Univ. at Karlsruhe, Germany / CS Dept. / IPD
\/1.3.18 ------------------------------------------ Germany --------
--
-- Uli
________---------------------------------------------------------------
\ / Ulrich Drepper / Univ. at Karlsruhe, Germany / CS Dept. / IPD
\/1.3.18 ------------------------------------------ Germany --------
> Trying to move from Microsoft C to GNU compiler is proving a little
> more akward than I anticipated.. certain functions such as getche()
> do not work are not available by the same name under GNU GCC. So, I
> would sincerely appreciate getting information 1) about the
> functions in GNU GCC/ G++ and two about any books or online docs
> that would have info about C programming under Linux.
>The question is simply wrong! First of all the things you asked about
>extensions of GCC has nothing to do with functions like getche(). The
>later come with the C Library. If dumb system like MSDOG don't have a
>system C Library it is their fault.
>Second the question correctly should be: which extension does
>*Microsoft* built in their C Library which prevents we from running on
>any other system. GNU/Linux follows the common standards (i.e. ANSI
>and POSIX) while Microsoft follows Microsoft standards.
Well, MS is an easy target, isn't it?
My C for PC reference book says that getche() is available in MSC
and TC but not in ANSI C. In other words, it has to be MS DOS-specific
and there's no reason for it to be available on Linux, Mac or Amiga DOS.
You need to check your sources for non-ANSI functions and replace them
with ANSI ones if you want your code to be portable.
BTW, why getche()? What was wrong with getchar()? :-|
Dimitri
---------------------------------------------------------------------------
All of the above is true in some sense, false in some sense, meaningless
in some sense, true and false in some sense, true and meaningless in some
sense, false and meaningless in some sense, and true and false and
meaningless in some sense.
-- Sri Syadasti Syadavaktavya Syadasti Syannasti.
---------------------------------------------------------------------------
> Trying to move from Microsoft C to GNU compiler is proving a little
> more akward than I anticipated.. certain functions such as getche()
> do not work are not available by the same name under GNU GCC. So, I
> would sincerely appreciate getting information 1) about the
> functions in GNU GCC/ G++ and two about any books or online docs
> that would have info about C programming under Linux.
> The question is simply wrong! First of all the things you asked about
> extensions of GCC has nothing to do with functions like getche(). The
> later come with the C Library. If dumb system like MSDOG don't have a
> system C Library it is their fault.
Again, there was no question. Furthermore, I often use Borland C underQuote:> Second the question correctly should be: which extension does
> *Microsoft* built in their C Library which prevents we from running on
> any other system. GNU/Linux follows the common standards (i.e. ANSI
> and POSIX) while Microsoft follows Microsoft standards.
I don't consider myself to be an expert on the subject, but wouldn't
the fact that GNU produces a C++ compiler make it, by definition,
non-ANSI compliant?
Hopefully he won't blame the rest of the posters in this newsgroup forQuote:> Don't blame the rest of the world for the bullsh*t this M$ concern
> produces.
I apologize to everyone else who has had to read this, I just
get pissed when I see people getting flamed for asking for help.
SBaker
> Trying to move from Microsoft C to GNU compiler is proving a little
> more akward than I anticipated.. certain functions such as getche()
> do not work are not available by the same name under GNU GCC. So, I
> would sincerely appreciate getting information 1) about the
> functions in GNU GCC/ G++ and two about any books or online docs
> that would have info about C programming under Linux.
Alan
--
..-----------,,----------------------------,,----------------------------,,
Redistribution of this message via the Microsoft Network is prohibited
<A href="file:/dev/mouse">Click here to disable mouse.</A>
1. bug in select function with GNU GCC 2.5.8 on Solaris 2.4?
I seem to have a problem with the select() function call using GNU GCC
compiler version 2.5.8 on Solaris version 2.4 and would like to know if
anyone else has seen this. In summary, multiple select()s testing for
read availability on a socket behaves oddly.
A simple test illustrates my problem - write a socket program that connects
to a remote-end echo server, writes some data, say 500 bytes, and select()s
and read()s the data back. A single select() and multiple read()s works fine,
but a sequence of select(), read() and then select(), read() again does not
work so well. What happens is that the second select() times after which
the data is indicated available, rather than returning immediately.
1. By using etherfind (on another SunOS machine) I know data is being
transmitted as expected on the network.
2. I have reset the arguments to select() correctly.
3. The same source compiled under SunOS 4.1.3 with GCC 2.5.8 works fine
on any SunOS or Solaris 2.3 machine, but fails likewise on a Solaris 2.4
machine. Hence I suspect Solaris 2.4 is at fault in some way w.r.t. the
select() implementation.
Can someone assist or tell me if I'm being dumb here? Much appreciated.
3. Shared libraries and GNU GCC using gas and gnu ld.
4. it's possible to compress file system transparently to the users?
5. Looking for info-ultrix/info-dec-unix or similar ...
6. Reading files created using VMS 'Backup'
7. function, function...who's got the function?
8. ipchains
9. Help Unix GNU C++, ultoa function
10. ftw(): File Tree Walk library function failes to compile on SCO OS5 w/ gnu.
11. What is the 64 bit stat function call name for C in GNU
12. HELP! PCI functions for GNU C++ ?
13. GNU's getline functions & PERL