[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: sdiff code error
From: |
Paul Edwards |
Subject: |
Re: sdiff code error |
Date: |
Sat, 4 Nov 2006 22:12:23 +1100 |
>>>> But writing to memory location 0 is not a good idea!
>>
>>> It doesn't actually do that.
>>
>> It doesn't?
> No, it doesn't.
What does it do then? That's what the code looked like to me.
>>> (Wondering what obsolete system that is, which does not have
>>> sigprocmask. :-) )
>>
>> I'm porting a lot of stuff to MVS 3.8 (IBM mainframe),
>> now that I have ported gcc 3.2.3 to it. It is a pure C89
>> environment. Text processing utilities should be
>> C89-compliant by default.
> Signal handling isn't exactly the best specified part of the C standard.
Text processing programs don't require signalling. They
should come out of the box as C89-compliant. If for some
reason you want to do non-standard things it should be
#define'd out by default.
BFN. Paul.
- sdiff code error, Paul Edwards, 2006/11/04
- Re: sdiff code error, Andreas Schwab, 2006/11/04
- Re: sdiff code error, Paul Edwards, 2006/11/04
- Re: sdiff code error, Andreas Schwab, 2006/11/04
- Re: sdiff code error,
Paul Edwards <=
- Re: sdiff code error, Andreas Schwab, 2006/11/04
- Re: sdiff code error, Paul Edwards, 2006/11/04
- Re: SPAM: Re: sdiff code error, Andreas Schwab, 2006/11/05
- sdiff code error, Paul Edwards, 2006/11/05
- Re: sdiff code error, Paul Eggert, 2006/11/04
- Re: sdiff code error, Paul Edwards, 2006/11/04
- Re: sdiff code error, Paul Eggert, 2006/11/05
- Re: sdiff code error, Paul Edwards, 2006/11/05