On Wed, 2014-06-04 at 21:15 -0400, Sam Varshavchik wrote:
> Adam Williamson writes:
>
> > Sam, this was clearly a half-baked thought Lennart threw out in passing.
> > It wasn't a formal proposal.
>
> I don't think there was any danger of anyone possibly considering that.
>
> > It's bad enough th
Adam Williamson writes:
Sam, this was clearly a half-baked thought Lennart threw out in passing.
It wasn't a formal proposal.
I don't think there was any danger of anyone possibly considering that.
It's bad enough that Slashdot et al pick this stuff up and then badly
misrepresent it; having
On Sun, 2014-04-27 at 19:12 -0400, Sam Varshavchik wrote:
> Can't wait for this latest howler from the great minds of Fedora to hit
> Slashdot.
NECRO ALERT
Still catching up on devel@ archives. This was an interesting thread to
read in retrospect (and much of it over my head), but I was partic
On Tue, Apr 29, 2014 at 12:08:11PM -0300, Paulo César Pereira de Andrade wrote:
> 2014-04-27 19:02 GMT-03:00 Andrew Price :
> > On 24/04/14 15:13, Lennart Poettering wrote:
> >>
> >> We probably should make setjmp()-freeness a requirement for
> >> all code included in Fedora.
> >
> >
> > Would it b
On Mon, Apr 28, 2014 at 2:24 AM, Florian Weimer wrote:
> On 04/28/2014 09:52 AM, Nikos Mavrogiannopoulos wrote:
>
> setjmp and longjmp are tools, that one may use in a good or bad way.
>> Along the same lines one could argue for dropping programs that use goto
>> in Fedora (because everyone know
2014-04-27 19:02 GMT-03:00 Andrew Price :
> On 24/04/14 15:13, Lennart Poettering wrote:
>>
>> We probably should make setjmp()-freeness a requirement for
>> all code included in Fedora.
>
>
> Would it be worth the effort, and how feasible is it anyway?
> - Do we have any usage statistics?
> - How
On 04/28/2014 03:49 PM, Adam Jackson wrote:
> On Mon, 2014-04-28 at 09:58 -0400, Casey Dahlin wrote:
>> On Mon, Apr 28, 2014 at 08:57:27AM -0400, Adam Jackson wrote:
>>> On Sun, 2014-04-27 at 23:02 +0100, Andrew Price wrote:
On 24/04/14 15:13, Lennart Poettering wrote:
> We probably should
2014-04-28 0:02 GMT+02:00 Andrew Price :
> On 24/04/14 15:13, Lennart Poettering wrote:
>
>> We probably should make setjmp()-freeness a requirement for
>> all code included in Fedora.
>>
>
> Would it be worth the effort, and how feasible is it anyway?
>
Generally no. Been there, done that.
Avo
On Mon, 2014-04-28 at 09:58 -0400, Casey Dahlin wrote:
> On Mon, Apr 28, 2014 at 08:57:27AM -0400, Adam Jackson wrote:
> > On Sun, 2014-04-27 at 23:02 +0100, Andrew Price wrote:
> > > On 24/04/14 15:13, Lennart Poettering wrote:
> > > > We probably should make setjmp()-freeness a requirement for
>
On 04/28/2014 02:57 PM, Adam Jackson wrote:
A completely arbitrary datapoint:
dmt:~% file /lib64/* | grep ELF.*shared | cut -f 1 -d : | xargs nm -aDu | grep
-c setjmp
79
Less arbitrary data point: 761 source packages in Fedora rawhide
reference any of the setjmp, _setjmp, or __sigsetjmp ELF
On Mon, 28 Apr 2014, Adam Jackson wrote:
A completely arbitrary datapoint:
dmt:~% file /lib64/* | grep ELF.*shared | cut -f 1 -d : | xargs nm -aDu | grep
-c setjmp
79
At a minimum you'd have to rewrite freetype, have fun with that.
I'm happy for libreswan/openswan to not use it, if someone
On Mon, Apr 28, 2014 at 08:57:27AM -0400, Adam Jackson wrote:
> On Sun, 2014-04-27 at 23:02 +0100, Andrew Price wrote:
> > On 24/04/14 15:13, Lennart Poettering wrote:
> > > We probably should make setjmp()-freeness a requirement for
> > > all code included in Fedora.
> >
> > Would it be worth the
On Mon, Apr 28, 2014 at 09:47:53 +0200,
Zoltan Boszormenyi wrote:
Just one datapoint: have fun rewriting PostgreSQL's error handling
while still keeping it portable and acceptable upstream. Not to mention
Cerberus (a.k.a. Tom Lane) who guards that entrance, reads this list and
IIRC is a Red H
On Sun, 2014-04-27 at 23:02 +0100, Andrew Price wrote:
> On 24/04/14 15:13, Lennart Poettering wrote:
> > We probably should make setjmp()-freeness a requirement for
> > all code included in Fedora.
>
> Would it be worth the effort, and how feasible is it anyway?
I don't think it'd be worth the e
Hi
On Mon, Apr 28, 2014 at 3:47 AM, Zoltan Boszormenyi wrote:
> Just one datapoint: have fun rewriting PostgreSQL's error handling
> while still keeping it portable and acceptable upstream. Not to mention
> Cerberus (a.k.a. Tom Lane) who guards that entrance, reads this list and
> IIRC is a Red
On Mon, 2014-04-28 at 10:10 +0100, Daniel P. Berrange wrote:
> > To the point, if a program uses setjmp and longjmp it is often that
> > there was no other way to do it. You cannot for example have a
> > co-routine/fiber implementation in C without setjmp() and longjmp().
> That's not correct - yo
On Mon, Apr 28, 2014 at 09:52:36AM +0200, Nikos Mavrogiannopoulos wrote:
> On Sun, 2014-04-27 at 23:02 +0100, Andrew Price wrote:
> > On 24/04/14 15:13, Lennart Poettering wrote:
> > > We probably should make setjmp()-freeness a requirement for
> > > all code included in Fedora.
> >
> > Would it b
On 04/28/2014 09:52 AM, Nikos Mavrogiannopoulos wrote:
setjmp and longjmp are tools, that one may use in a good or bad way.
Along the same lines one could argue for dropping programs that use goto
in Fedora (because everyone knows that goto is bad).
All compliant uses of setjmp/longjmp can be
Dne 28.4.2014 09:52, Nikos Mavrogiannopoulos napsal(a):
On Sun, 2014-04-27 at 23:02 +0100, Andrew Price wrote:
On 24/04/14 15:13, Lennart Poettering wrote:
We probably should make setjmp()-freeness a requirement for
all code included in Fedora.
I love the idea, but ...
Would it be worth the
2014-04-28 09:52 keltezéssel, Nikos Mavrogiannopoulos írta:
On Sun, 2014-04-27 at 23:02 +0100, Andrew Price wrote:
On 24/04/14 15:13, Lennart Poettering wrote:
We probably should make setjmp()-freeness a requirement for
all code included in Fedora.
Would it be worth the effort, and how feasibl
On Sun, 2014-04-27 at 23:02 +0100, Andrew Price wrote:
> On 24/04/14 15:13, Lennart Poettering wrote:
> > We probably should make setjmp()-freeness a requirement for
> > all code included in Fedora.
>
> Would it be worth the effort, and how feasible is it anyway?
setjmp and longjmp are tools, tha
2014-04-28 00:02 keltezéssel, Andrew Price írta:
On 24/04/14 15:13, Lennart Poettering wrote:
We probably should make setjmp()-freeness a requirement for
all code included in Fedora.
Would it be worth the effort, and how feasible is it anyway?
- Do we have any usage statistics?
- How often do
Rahul Sundaram writes:
Hi
On Sun, Apr 27, 2014 at 7:12 PM, Sam Varshavchik wrote:
According to its manpage, setjmp and longjmp conform to C89, C99, and
POSIX. I'm afraid I just can't wrap my brain around a concept of something
that's good enough for POSIX, but not good enough fo
Hi
On Sun, Apr 27, 2014 at 7:12 PM, Sam Varshavchik wrote:
>
> According to its manpage, setjmp and longjmp conform to C89, C99, and
> POSIX. I'm afraid I just can't wrap my brain around a concept of something
> that's good enough for POSIX, but not good enough for Fedora.
>
Just because a API
Andrew Price writes:
On 24/04/14 15:13, Lennart Poettering wrote:
We probably should make setjmp()-freeness a requirement for
all code included in Fedora.
Would it be worth the effort, and how feasible is it anyway?
- Do we have any usage statistics?
- How often do we see bugs caused by bad u
On 24/04/14 15:13, Lennart Poettering wrote:
We probably should make setjmp()-freeness a requirement for
all code included in Fedora.
Would it be worth the effort, and how feasible is it anyway?
- Do we have any usage statistics?
- How often do we see bugs caused by bad uses of setjmp/longjmp?
26 matches
Mail list logo