Issue 6171 - Kill or fix K&R support
Summary: Kill or fix K&R support
Status: VERIFIED SUSPENDED
Alias: None
Product: OpenLDAP
Classification: Unclassified
Component: slapd (show other issues)
Version: unspecified
Hardware: All All
: --- normal
Target Milestone: ---
Assignee: OpenLDAP project
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-12 15:00 UTC by Hallvard Furuseth
Modified: 2021-08-03 17:59 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description Hallvard Furuseth 2009-06-12 15:00:33 UTC
Full_Name: Hallvard B Furuseth
Version: 2.0.0 and later
OS: 
URL: http://www.openldap.org/lists/openldap-devel/200706/msg00009.html
Submission from: (NULL) (129.240.6.233)
Submitted by: hallvard


openldap-devel thread "Kill K&R C support?" from jun 2007,
edited into a single quote/response stream:

Hallvard B Furuseth wrote:
>Kurt Zeilenga wrote:
>>Hallvard B Furuseth wrote:
>>> As far as I can tell, OpenLDAP has been unusable with K&R C since
>>> openldap-2.0:  lber.h in that release had prototypes unprotected
>>> by LDAP_P() in struct sockbuf_io.  They've been there ever since.
>>> So LDAP_P() can [edit: probably] go.
>>
>> I note that the intent was to allow use of -lldap/-llber in K&R C
>> programs, but to require ISO C to build OpenLDAP Software.
>
> Which I think made sense.  But now, apparently nobody has complained
> about the problem for 7 years.  Time to quit worrying about K&R?
> 
>> Seems the former is broken (lber.h issues).

Still broken today (jun 2009).

>>> Don't know which other not-strict-ISO support is still useful -
>>> I note lber.h has used <string.h> since openldap-2.2.4, for example.
>>> libldap/open.c has used <limits.h> since 2.0.0.
>>
>> The latter isn't a problem with regard to the above intent.
>>
>>> HEAD wraps that
>>> in HAVE_LIMITS_H, but it does not protect INT_MAX the same way.
>>
>> Likewise.
Comment 1 Howard Chu 2009-06-23 21:48:18 UTC
moved from Incoming to Development
Comment 2 Quanah Gibson-Mount 2021-01-11 17:22:08 UTC
If someone eventually hits an issue where they need K&R support, we can fix the header files.  No one has run into this as a significant issue in 20 years.