Talk:Alloy Analyzer

Removed paragraph
I just removed the following content from the article:


 * Alloy is very useful in teaching. While a student is programming, it actually shows his or her errors on the screen as they are being coded.  This alleviates the frustration of an unbearable amount of errors being displayed on the students screen at compilation time.

I've taken this content out for two reasons:
 * 1) The tone is not all that encyclopedic, but sounds more like marketing to me.
 * 2) It's not clear to me what the paragraph in question is talking about. The article is about the Alloy language. The paragraph appears to be talking about some kind of tool for use with the Alloy language, but doesn't say which one.

Can anyone clarify what tool is being discussed? (I freely admit that my familiarity with Alloy is extremely limited, although I look forward to having some time to investigate it further) Once we have that figured out, we can rewrite the paragraph to a more encyclopedic tone, and reinsert it. --Allan McInnes (talk) 19:28, 20 April 2006 (UTC)


 * Ok, the removed content seems (from a quick glance at the Alloy FAQ) to have been talking about the Alloy Analyzer. I've added a more general paragraph which discusses the Analyzer's capability for incremental analysis. --Allan McInnes (talk) 19:36, 20 April 2006 (UTC)

Decidable, not Tractable
The bound on the analysis is necessary, not to make it tractable per se, but to make the analysis decidable at all. No automatic analysis can find solutions to general first-order logic. Progressnerd (talk) 17:37, 4 April 2008 (UTC)

Broken link
The link #2 is broken. A possible alternative is the direct link to the workshop proceedings (pages 100-104): http://alloy.mit.edu/workshop/proceedings/workshop-proceedings.pdf --Scimiot (talk) —Preceding undated comment added 11:17, 6 January 2013 (UTC)