On Monday, January 27, 2014 9:35:55 AM UTC-8, Georgi Guninski wrote: > > On Mon, Jan 27, 2014 at 06:19:34PM +0100, Jeroen Demeyer wrote: > > On 2014-01-27 15:13, Georgi Guninski wrote: > > >On Mon, Jan 27, 2014 at 03:07:00PM +0100, Jeroen Demeyer wrote: > > >>On 2014-01-27 14:35, Jeroen Demeyer wrote: > > >>>Use cancel_alarm(). I agree this should be documented in alarm(). > > >> > > >>This is now http://trac.sagemath.org/ticket/15743 and needs review. > > >> > > > > > >May I ask you to allow alarm(0) again since other people > > >might use it too? > > > > The problem is that I didn't want to define alarm(x) for small > > values of x. The question becomes more difficult if you need to > > think about what > > > > alarm(0.0) > > > > and > > > > alarm(1e-300) > > > > should do. > > > > > I see. > > You have a problem and you broke my code, > f.cking backward compatibility, make me > fix it. > > On linux: > $man alarm > > If seconds is zero, no new alarm() is scheduled. > In any event any previously set alarm() is canceled. >
First, please try to be more polite. Second, the old alarm code happened to work the way you wanted, but it wasn't documented that way, and it's not clear (to me, at least) that that use was ever intended. Had it been documented, or had it been commonly known that alarm(0) was used that way, backwards-compatibility would have been preserved. -- John -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/groups/opt_out.
