Opened 8 years ago

Last modified 7 years ago

#58 new defect

source code highlighting

Reported by: ke Owned by: ke
Priority: minor Milestone:
Component: kahina-swi Version:
Keywords: Cc:

Description

These are (I believe) the rules for highlighting source code which SWI-Prolog's graphical tracer follows, and which we should probably imitate (by reusing their Prolog code):

  • at call ports: highlight the goal in the body in which it occurs, if that body is visible, else highlight the first clause (which is applicable as determined by first-argument indexing?) of the called predicate
  • at exit ports: highlight the end (period sign) of the successful clause
  • at redo ports: highlight the end (period sign) of the previously successful clause
  • at fail ports: highlight the head of the failed clause, if that clause is visible, else highlight the failed goal in the body of the clause in which it occurs (this is the inverse of the call case, so to speak)

SWI-Prolog's tracer has other, specialized ports that we need to investigate.

At the moment, we don't have clause-level highlighting, only predicate-level highlighting. This is also the reason why we don't see bound arguments at exit ports.

Change History (5)

comment:1 Changed 8 years ago by xrumer

  • Summary changed from Kahina for SWI-Prolog: source code highlighting to Xrumer Forums

In need of Xrumer files? check out the Xrchat forums!

comment:2 Changed 8 years ago by ke

  • Summary changed from Xrumer Forums to Kahina for SWI-Prolog: source code highlighting

comment:3 Changed 7 years ago by ke

  • Owner changed from somebody to ke

comment:4 Changed 7 years ago by ke

  • Component changed from core to kahina-swi

comment:5 Changed 7 years ago by ke

  • Summary changed from Kahina for SWI-Prolog: source code highlighting to source code highlighting
Note: See TracTickets for help on using tickets.