alternate evaluation strategy with fewer glitches?
17 views
Skip to first unread message
philip k
unread,
Feb 13, 2012, 12:12:19 PM2/13/12
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Flapjax
Hi,
I just read the thesis paper on Flapjax and was under the impression
that the breadth-first evaluation scheme presented there would
eliminate all glitches. However, the latest github commit message
suggests otherwise - can somebody explain the exact nature of the
glitches that the new evaluation strategy attempts to rule out?
Also a short explanation of how this is done would be very helpful.
Thanks a lot!
Arjun Guha
unread,
Feb 13, 2012, 1:32:47 PM2/13/12
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to fla...@googlegroups.com
Haha. Yeah. The strategy presented in the Flapjax paper is sound, but it's tricky to implement correctly. I have a small variant of the Flapjax paper's strategy that's easier to implement and fixes some bugs. (It's still doing breath-first traversal, so nothing dramatically different.)
I'm traveling over the next two weeks. I'll do a writeup when I'm back.