I guess we can add another special case. -- Yehuda
On Wed, Feb 4, 2009 at 9:23 AM, Shalon Wood <[email protected]> wrote: > > > Hmm. What about having it crash in production and test, but not > development? That should solve the problem of crashing during > development, but still ensure there aren't any lurking surprises in > production. (My rationale for crashing in the test environment is that > that will keep from wasting time running tests, thus speeding things > up). > > Shalon Wood > > Yehuda Katz <[email protected]> writes: > > > We previously crashed on syntax error, but that drove people nuts who > > saved with syntax errors and had their app crash. Apparently people > hit > > save with syntax errors and having their app crash before they got a > > chance to fix it was driving them nuts. > > -- Yehuda > > > > On Wed, Feb 4, 2009 at 8:24 AM, Shalon Wood <[email protected]> wrote: > > > > I just ran into a situation that threw me; I had a syntax error in > > my controller > > file which stopped it from being loaded, but instead of throwing an > > error immediately and refusing to continue (as I would have > > expected), I > > got an error about not being able to find the controller class > > later, > > when my tests attempted to use the controller. > > I would think that it would be better to throw an error and die on > > startup, since a syntax error in a controller is _never_ good, and > > if > > the error doesn't show up until you access the page, you've > > potentially > > lost the information as to what the actual problem was, if you've > > rolled > > your logfile (e.g., a controller which is rarely used, perhaps once > > a > > month). > > Is there a reason for continuing after a syntax error in a > > controller > > (or model, for that matter)? > > Shalon Wood > > -- > > > > -- > > Yehuda Katz > > Developer | Engine Yard > > (ph) 718.877.1325 > > > -- > > > > -- Yehuda Katz Developer | Engine Yard (ph) 718.877.1325 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/merb?hl=en -~----------~----~----~----~------~----~------~--~---
