Boost logo

Boost-Build :

Subject: Re: [Boost-build] Debugger for Jam
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2015-03-22 15:40:55


On 03/22/2015 01:07 PM, Aaron Boman wrote:
> I've been playing around with your debugger. One thing I noticed was
> that specifying Jamfile<C:\path\to\my\Jamroot.jam>.my-rule won't work
> due to the colon in the path. I temporarily circumvented the problem by
> specifying Jamroot.jam:<line-number>. Other than that it works really well.

Thanks. I'll adjust the code to check for ".+:\d+$"
instead of just ".*:.*".

> For the interpreter stuff, I've made similar changes to parse.c and
> scan.c, so I'll rebase my changes on top of yours and use the existing
> functionality you've provided as its more complete than what I have. I
> plan on creating a builtin EXEC_STRING function that will do nothing
> more than call parse_string.

Perhaps also we should make parse_string return
an error code instead of aborting on parse errors.

> What are your thoughts on allowing execution of arbitrary snippets of
> code? Perhaps default to interpreter functionality if a valid command
> isn't provided? For example, being able to alter the running code by
> changing a value. Or another example, being able to import some utility
> rule.

   This paragraph is talking about the debugger
again, right? My intention was to follow gdb's
interface as closely as possible. Right now,
you can execute a rule call from print. I haven't
looked up what commands gdb provides for modifying
the program's state, yet.

In Christ,
Steven Watanabe

Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at