[ic] Require should mean require

Gert van der Spoel gert at 3edge.com
Thu Jun 25 14:19:54 UTC 2009

> -----Original Message-----
> From: interchange-users-bounces at icdevgroup.org [mailto:interchange-
> users-bounces at icdevgroup.org] On Behalf Of Jon Jensen
> Sent: Thursday, June 25, 2009 5:02 PM
> To: interchange-users at icdevgroup.org
> Subject: [ic] Require should mean require
> Folks,
> I don't believe I knew before that the "Require" global directive
> doesn't
> actually raise a fatal error if the required module doesn't exist or
> fails
> to load. Yet that is the case.
> To me this seems inconsistent, since the "Require" catalog directive is
> fatal for that catalog if there's an error.
> I propose changing this, so that any missing modules will cause
> Interchange to fail to start rather than causing only a warning which
> isn't even seen on unattended restarts such as at reboot.
> This patch changes the behavior strictly for Require module:
> http://github.com/jonjensen/interchange/commit/7e3974960594da194b8f585e
> 3e761322ef8df72f
> But I would like to discuss making all the Require types die on
> failure,
> rather than just being warnings. It saves a lot of frustration to have
> Interchange scream loudly when there's a problem instead of finding out
> about it only later when things start to fail mysteriously.
> Please comment if you object to such a change.

I never really understood the idea of just a warning, knowing that it was
not going to work eventually. Always paying attention when restarting, but
good point for the automatic restarts.

+1 , 

More information about the interchange-users mailing list