I see bad things come of this. You wouldn't know what the last compiled code actually looked like. And how many of us would leave uncompleted scripts for months?

YES!!! I end up scraping my errorr-ed script and storing outside of notes in a text file - how can that be good? Let me "Save with Errors"
@1 (Tom): maybe it would create a replication conflict design element or something - and the last compiled code is the "real one". Sometimes I just want to get an idea down and sketched out without actually finishing the agent. This code wouldn't compile, but it would at least let me go home at night when I'm so tired I can't code any more!

@1 - I may copy a script library/agent/form/etc and then edit/refactor that copy. In effect I create a "branch" which does not have any effect on the "trunk" as it is not part of it. Then I refactor it and when I am ready I merge it back into the trunk replacing the original design element.

I am not saying deploy a template which does not entirely compile, but I don't think you are either. Obviously this is a feature that would be hugely useful in development.

Back on branching, I may also want to create a branch at the database level. I would copy a whole database and then mess around with it wanting to save my work before I have finished all the changes. This would be useful if I have to change multiple related design elements.

@1 - Consider this:
Syntax errors are only one kind of errors. The other are logic errors, not to mention misinterpreted requirements, over-engineered implementation, ... These "errors" are not caught by the compiler and can persist in the code until the effects become quite noticeable and costly. And arguably the effects of these errors are orders of magnitude greater in their impact.

After a long period of time doing LotusScript development I spent a period of time doing C# development with Visual Studio. Whilst there were a lot of things in Visual Studio that I loved, one of the things I grew to hate was that it allowed me to save code changes even when it didn't compile. Sometimes an innocent change would take forever to resolve (e.g. removing just one of those "{"s). Then I would just wish I could go back to the last compile and start again. With Domino Designer if my changes start to cause compile errors I know that I have an easy way to get back to that last safe point. Code managemnt modules like CIAO only take me back to the last time I did a Check Out.

%REM
Buggy Code - Fix later
%END REM