Making an IDE using Pascal Script and SynEdit

views:

708

answers:

+7 Q:

Making an IDE using Pascal Script and SynEdit

Hi, I'm creating a built-in script engine using PascalScript from RemObjects (excellent) and the SynEdit editor. It's almost finished using the IDE example shipped with PascalScript and the IDE example in SynEdit - but - I can't see how to ask PascalScript whether a numbered source line is 'executable' or not. (I can then use this to mark the SynEdit gutter with the 'Delphi blue dot'). I guess I might have to do a dissassembly of the ROPS output?

Any PascalScript experts here? THanks. Brian.

+1 A:

I don't know exactly how it does it, but the IDE project in the PascalScript package (found under \samples\debug ) is able to offer Step Into and Step Over (F7 and F8) functionality, so logically it has to have some way of associating PS bytecode with lines of script code. Try examining that project to see how it does it. As a bonus, it uses SynEdit too, so the ideas will be easy to adapt to your own system.

Mason Wheeler 2009-06-26 19:50:57

Thanks for the comment Mason. I'v been using that example a lot. The StepInto and StepOver are built into the TPSDebugScript class and not surprisingly they get their 'I'v ended up at this new line' by actually executing the code. Before the code gets executed, I need to query the script code for possible lines and that's the bit that flumoxing me. Bri

Brian Frost 2009-06-26 21:17:15

How does it map code to source lines? There's not a 1:1 relationship. Consider "x := 5;" and "x := 5 * performCalculation(y, z + x);" Both are a single line, but the second one contains a lot more operations to be performed. There has to be some sort of metadata mixed in with the bytecode that it uses to do the mapping.

Mason Wheeler 2009-06-26 21:26:28

@Mason: Look into TPSCustomDebugExec.TranslatePositionEx(). It has the source position in the debug info records, and for every op it can look up the source position info. For your second example all those operations would return the stored source position of the first operation in that line.

mghie 2009-06-26 21:51:47

+7 A:

Have a look at the source code of Inno Setup. It does show a small dot in the SynEdit gutter area for lines with executable code, gray ones for lines that are executable but have not been executed, green ones for lines that have been hit at least once.

The code for this can be found in CompForm.pas, look for the TLineState type. The information is set up in the iscbNotifySuccess state of the compiler callback, you could do the same in your IDE. You may need to adapt the code to handle multiple source files, as the Inno Setup compiler deals with code snippets in the single source file only.

In the Pascal Script sources you should have a look at the TPSCustomDebugExec.TranslatePositionEx() method - it does return the name of the source file as well.

mghie 2009-06-26 21:34:17

Great idea. I knew Innosetup used PascalScript but I'd not realised that it had the edit features. Off to look. Thanks.

Brian Frost 2009-06-26 21:43:22

mghie, your suggestion was excellent. That had all the info I needed. Regards, Brian.

Brian Frost 2009-06-29 14:51:25

ansaurus

tags:

views:

answers:

Making an IDE using Pascal Script and SynEdit

related questions