muesli - Tasks: task #10231, Interface to Guile
You are not allowed to post comments on this tracker with your current authentication level.
task #10231: Interface to Guile
Submitter: | John Sturdy <johnsturdy> | ||
Submitted: | Thu 04 Mar 2010 04:53:44 PM UTC | ||
Should Start On: | Thu 04 Mar 2010 12:00:00 AM UTC | Should be Finished on: | Thu 04 Mar 2010 12:00:00 AM UTC |
Category: | None | Priority: | 6 |
Status: | Ready For Test | Privacy: | Public |
Assigned to: | None | Percent Complete: | 100% |
Open/Closed: | Open | Effort: | 0.00 |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 2 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2010-03-15 | johnsturdy | Status | None | Ready For Test | |
Percent Complete | 0% | 100% |
Powered by Savane 3.13-758e.
Corresponding source code
We should interface to Guile. This may be slightly less straightforward than the others, as it requires one of its own stackframes on the stack outside the application's frames --- or might it be alright to have the special frame between our call of Guile and any actual Guile code? I'll either piece this out from the code, or track down some Guile hackers to ask.