Subject: Linux-Development Digest #970
From: Digestifier <Linux-Development-Request@senator-bedfellow.MIT.EDU>
To: Linux-Development@senator-bedfellow.MIT.EDU
Reply-To: Linux-Development@senator-bedfellow.MIT.EDU
Date:     Mon, 1 Aug 94 07:13:07 EDT

Linux-Development Digest #970, Volume #1          Mon, 1 Aug 94 07:13:07 EDT

Contents:
  Re: lint for linux (Derek Jones)
  why does backspace not send backspace ?? (Andre Schroeter)
  Truecolor support for XFree86? (William Hoffman)
  Re: lint for linux (Thomas G. McWilliams)
  DBM does not Work ! (Howard Anderson RVS-ISG)
  Re: lint for linux (Mitchum DSouza)

----------------------------------------------------------------------------

From: D.G.Jones@scuna.dircon.co.uk (Derek Jones)
Subject: Re: lint for linux
Date: 1 Aug 1994 02:50:40 -0400
Reply-To: D.G.Jones@scuna.dircon.co.uk (Derek Jones)

Sigh, again,

I have responded privately to some of the people who have
said "gcc does everything" over the last few months
but now feel it's time for the list.

gcc -Wall -pedantic does *not* catch some of the (even
more trivial) errors that a decent lint will catch. *Esp.*
if those errors are *calling problems between* source files.

I did some tests on this about 18 months ago and showed the
problem with a very simple set of source files. I think at
the time the discussion was on the turbo-c list or somesuch.

I don't have access to a lint currently, (since I'm running
Linux 8-), so I can't immediately repeat it for everyone
but I may be able to in a few weeks.

Kind regards to all

Derek

================================================================================
Derek Jones                                          !SCUNA Computer Consultancy
Computer Consultant                                  ! 53 Archer Road, Sheffield
SCUNA (Systems,C,UNIX,Networking,Advice)             !                    S8 0JT
Email: D.G.Jones@scuna.dircon.co.uk                  !                        UK
WWW: http://scuna.dircon.co.uk/public_html/scuna.html!       Tel: +44 742 555524
================================================================================


------------------------------

From: andre@borneo.dkfz-heidelberg.de (Andre Schroeter)
Subject: why does backspace not send backspace ??
Date: Mon, 01 Aug 94 09:13:45 CET

why is the default keymap configured not to send backspace when backspace
is pressed?
why are all loadable maps configured to send delete if backspace is pressed?
why is the stty defaut for the erase key "^?" ?
why is it right under X ?

thank you
  andre schroeter
-- 
================================================================================
Andre Schroeter                         German Cancer Research Center
tel.: (+49) 6221 - 42 2382              Dept. Medical and Biological Informatics
fax.: (+49) 6221 - 42 2345              Im Neuenheimer Feld 280
e-mail: A.Schroeter@DKFZ-Heidelberg.de  D-69120 Heidelberg, Germany
================================================================================

------------------------------

From: wmhoffma@crab.rutgers.edu (William Hoffman)
Subject: Truecolor support for XFree86?
Date: 29 Jul 94 04:43:11 GMT

I've been wondering if there is any effort being made to add truecolor
and/or hicolor support to XFree86.  I have a truecolor capable card,
and it really makes me puke to have to boot DOS and run Windoze in
order to get 24-bit color.  Can anyone enlighten me?

George Hoffman

------------------------------

From: tgm@netcom.com (Thomas G. McWilliams)
Subject: Re: lint for linux
Date: Mon, 1 Aug 1994 08:48:17 GMT

Derek Jones (D.G.Jones@scuna.dircon.co.uk) wrote:
: gcc -Wall -pedantic does *not* catch some of the (even
: more trivial) errors that a decent lint will catch. *Esp.*
: if those errors are *calling problems between* source files.

I agree with you. Basically gcc only operates over one source
file at a time, and it can not do global optimization. That is
why gcc ultimately fails as a replacement for a full throttle
testosterone pumped hair on your back lint. Of course full
strict ansi prototypes in your application's header files can
catch most of the serious calling problems between source
files. But it would be nice to have warnings about symbols that
could be declared static for instance.

tgm@netcom.com


------------------------------

From: hwa@ua.nrb.ac.uk (Howard Anderson RVS-ISG)
Subject: DBM does not Work !
Date: Mon, 1 Aug 1994 10:13:04 GMT



I am using Linux Kernel 1.0.9, from Slackware release 2.0.0.

I just tried porting a working application using ndbm on sunos 4.1.3 to Linux. Any calls
to dbm_open, dbm_close, dbm_fetch or dbm_store return error conditions. Since dbm_open
fails (returning a NULL datum) I cannot createa dbm file to check the reading of an 
existing file. On investigation I found that the dbm used is GNU-ndbm with a 1993 copyright
date. Does anyone know if this problem is restricted to Salackware ??? should I 
investigate the port of GNU-ndbm to Linux, and possibly prodcue another, or is there a 
fixed version around on the net ???? If there Is, I will advise the creator of Slackware
to update his version.
--

Howard Anderson 

N.E.R.C Research Vessel Services
Barry
S. Glamorgan
Wales

hwa@unixa.nerc-barry.ac.uk

The above opinions are my own not my employers.

Linux is THE free operating system.

------------------------------

From: Mitchum.DSouza@mrc-apu.cam.ac.uk (Mitchum DSouza)
Subject: Re: lint for linux
Date: 1 Aug 1994 10:51:00 GMT

In article <tgmCtuLsH.5zF@netcom.com>, tgm@netcom.com (Thomas G. McWilliams)
writes:
|> Derek Jones (D.G.Jones@scuna.dircon.co.uk) wrote:
|> : gcc -Wall -pedantic does *not* catch some of the (even
|> : more trivial) errors that a decent lint will catch. *Esp.*
|> : if those errors are *calling problems between* source files.
|> 
|> I agree with you. Basically gcc only operates over one source
|> file at a time, and it can not do global optimization. That is
|> why gcc ultimately fails as a replacement for a full throttle
|> testosterone pumped hair on your back lint. Of course full
|> strict ansi prototypes in your application's header files can
|> catch most of the serious calling problems between source
|> files. But it would be nice to have warnings about symbols that
|> could be declared static for instance.

I dunno if you guys caught the free-lint announcement (not the type in found
in your common pocket). I haven't had a chance to compile/port the source,
so if you fancy something better that "gcc -plethora-of-options" then look
under

        larch.lcs.mit.edu:/pub/Larch/

or the URL if you prefer is at

        http://larch-www.lcs.mit.edu:8001/larch

Mitch

------------------------------


** FOR YOUR REFERENCE **

The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:

    Internet: Linux-Development-Request@NEWS-DIGESTS.MIT.EDU

You can send mail to the entire list (and comp.os.linux.development) via:

    Internet: Linux-Development@NEWS-DIGESTS.MIT.EDU

Linux may be obtained via one of these FTP sites:
    nic.funet.fi				pub/OS/Linux
    tsx-11.mit.edu				pub/linux
    sunsite.unc.edu				pub/Linux

End of Linux-Development Digest
******************************
