Because it applies to imp3, mnemo, nag, turba, kronolith, sork-passwd, 
if i remember all i have installed. I though reporting it once and for 
horde is better than reporting it six times...

After all, all these belong to horde, and it clearly looks like common 
code: same filename, same structure, same comments...

You filed this ticket in the Horde Framework category, with no version 
information.

Well, then have a look at your IMP3 version 3.2.6 tarball, released 
last month.

in lib/base.php, line 55:

http://cvs.horde.org/co.php/imp/lib/base.php?r=1.24.2.5#55



I bet it is the same with the other packages - i don't think the 
debian maintainer will re-add the set_time_limit statement.



Sorry, i'm a bit annoyed to re-change this thing every time a new 
version is uploaded to debian to get imp&co working again... actually 
mostly because i forget each time to do so again.

Every place that calls set_time_limit() where it is conceivably a good 
idea to silence warnings has them silenced already. set_time_limit() 
is called in Registry.php where it should. Try submitting a better and 
more accurate report the next time you open a ticket, and lose the 
superior attitude.

Apparently using

   @set_time_limit(...);

works fine, so instead of removing these statements you could just 
have added the "at" char - which will silence the warning. At least it 
does so on my test system.



Learn your php api. ;-)