I see. Instead of "more compatible" can you instead rewrite the sentence to say what one might gain out that extra compatibility? If not, I think the equation below gives you license to just remove the word "more". FWIW.
Robby On Fri, Apr 2, 2010 at 12:37 PM, Jay McCarthy <[email protected]> wrote: > Before it was not compatible. > > Now we can't find any C-generated zos that fail the test: > > (equal? (parse c) (parse (emit (parse c)))) > > But almost everything fails > > (equal? c (emit (parse c))) > > So it is more compatible than before... but we don't believe it is a > re-implementation. > > This matters though, because the decompiler would error on some zos or > give the wrong answer, but now it doesn't. > > Jay > > On Fri, Apr 2, 2010 at 12:21 PM, Robby Findler > <[email protected]> wrote: >> What does "more compatible" mean (in bullet 5)? >> >> Robby >> >> On Fri, Apr 2, 2010 at 12:19 PM, Eli Barzilay <[email protected]> wrote: >>> Mail me if you have any last-minute changes. Also, Sam: I need that >>> improved entry. >>> >>> ---------------------------------------------------------------------- >>> * PLT now supports multi-core parallelism via futures. Futures >>> create tasks that run in parallel, as long as the tasks stay in >>> the "fast path" of the runtime system. For more information, see: >>> http://tinyurl.com/futuresguide . >>> >>> * Our unit testing framework, schemeunit, is now included in the >>> distribution. A graphical test runner is available via >>> schemeunit/gui. >>> >>> * New Russian and Ukranian translations, thanks to Sergey Semerikov. >>> >>> * The support languages for the "Programming Languages: Application >>> and Interpretation" textbook by Shriram Krishnamurthi are now part >>> of PLT Scheme. In addition the PLAI GC language comes with a >>> random mutator generator (to help test collectors) and an improved >>> heap visualizer. >>> >>> * The Scheme-implemented bytecode reader, writer, and decompiler is >>> now more compatible with the C-implemented bytecode reader and >>> writer. >>> >>> * The `scheme/class' library now provides contract combinators for >>> classes (`class/c') and objects (`object/c'). See the Reference >>> and Guide for details. Also, a backwards-compatible >>> `object-contract' version of `object/c' has replaced the old >>> `object-contract' combinator. >>> >>> * Writing new kinds of contracts is now easier with keyword-based >>> constructors (`make-contract' and `make-flat-contract'), a >>> simpler set of structure properties (`prop:contract' and >>> `prop:flat-contract'), and the introduction of blame objects for >>> tracking contract metadata. >>> >>> * A number of improvements to Redex's typesetting facilities. >>> >>> * The language dialog now suggests using "#lang" more strongly as >>> the default language. DrScheme no longer uses the term `Module >>> language'. >>> ---------------------------------------------------------------------- >>> -- >>> ((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay: >>> http://barzilay.org/ Maze is Life! >>> _________________________________________________ >>> For list-related administrative tasks: >>> http://list.cs.brown.edu/mailman/listinfo/plt-dev >>> >> _________________________________________________ >> For list-related administrative tasks: >> http://list.cs.brown.edu/mailman/listinfo/plt-dev >> > > > > -- > Jay McCarthy <[email protected]> > Assistant Professor / Brigham Young University > http://teammccarthy.org/jay > > "The glory of God is Intelligence" - D&C 93 > _________________________________________________ For list-related administrative tasks: http://list.cs.brown.edu/mailman/listinfo/plt-dev
