Re: The *scrapping* of setjmp/longjmp :-(

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Maiko Langelaar (ve4klm) wrote:
> what I would like to know is why did support for the JMPBUF
> mechanism suddenly get removed from GLIBC without any regard to existing
> applications that strongly depend on it.

The jmpbuf implementation is and has always been an implementation
detail which is not available to application.  The structure or the
constants to access it were only exposed because of historic accidents.
 In the older days we didn't hide the details.

But your $SUBJECT is of course wrong and deliberately confrontational.
Nobody removed setjmp and longjmp.  The interfaces are all there.  You
just cannot use them in an incorrect way anymore.

Fix your application.

-- 
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖

Attachment: signature.asc
Description: OpenPGP digital signature

-- 
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux