search

ags799 / aldb

The Alloy Debugger
MIT License
0 stars 0 forks source link

Parse Instance Description #3

Open ags799 opened 9 years ago

ags799 commented 9 years ago

aldb should allow its users to define an instance and attempt to run it through their Alloy model.

Initially, they will define their instances through text files. We need to be able to parse this text.

The parser will expect the same language that the Alloy Analyzer creates in its instance visualizer, when you click on 'Txt'.

ags799 commented 9 years ago

Useful stuff from Alloy: alloy4compiler.parser.CompUtil.parseOneExpression_fromString alloy4compiler.parser.CompUtil.parseEverything_fromFile alloy4compiler.sim.*

ags799 commented 9 years ago

More useful stuff from Alloy: alloy4.OurConsole.do_command

ags799 commented 9 years ago

Also: alloy4whole.SimpleGUI line 1652

hayesconverse commented 9 years ago

I can’t seem to find these in the source code. Could you give me a path or a github link? On Oct 16, 2014, at 2:20 PM, ags799 notifications@github.com wrote:

Also: alloy4whole.SimpleGUI line 1652

— Reply to this email directly or view it on GitHub.

ags799 commented 9 years ago

Those are in the Alloy Analyzer's code.

On Thu, Oct 16, 2014 at 2:28 PM, hayesconverse notifications@github.com wrote:

I can’t seem to find these in the source code. Could you give me a path or a github link? On Oct 16, 2014, at 2:20 PM, ags799 notifications@github.com wrote:

Also: alloy4whole.SimpleGUI line 1652

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub https://github.com/ags799/aldb/issues/3#issuecomment-59416498.

hayesconverse commented 9 years ago

Found it, thanks. Hadn’t looked under sdg.

-Hayes On Oct 16, 2014, at 2:32 PM, ags799 notifications@github.com wrote:

Those are in the Alloy Analyzer's code.

On Thu, Oct 16, 2014 at 2:28 PM, hayesconverse notifications@github.com wrote:

I can’t seem to find these in the source code. Could you give me a path or a github link? On Oct 16, 2014, at 2:20 PM, ags799 notifications@github.com wrote:

Also: alloy4whole.SimpleGUI line 1652

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub https://github.com/ags799/aldb/issues/3#issuecomment-59416498.

— Reply to this email directly or view it on GitHub.

ags799 commented 9 years ago

Oh yeah, everything's in there. Should have mentioned that, sorry.

On Thu, Oct 16, 2014 at 2:34 PM, hayesconverse notifications@github.com wrote:

Found it, thanks. Hadn’t looked under sdg.

-Hayes On Oct 16, 2014, at 2:32 PM, ags799 notifications@github.com wrote:

Those are in the Alloy Analyzer's code.

On Thu, Oct 16, 2014 at 2:28 PM, hayesconverse notifications@github.com

wrote:

I can’t seem to find these in the source code. Could you give me a path or a github link? On Oct 16, 2014, at 2:20 PM, ags799 notifications@github.com wrote:

Also: alloy4whole.SimpleGUI line 1652

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub https://github.com/ags799/aldb/issues/3#issuecomment-59416498.

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub https://github.com/ags799/aldb/issues/3#issuecomment-59417380.

ags799 commented 9 years ago

Perhaps the user should be writing XML. Consider http://alloy.mit.edu/alloy/code/EvaluatorExample.java.html