Re: [Pharo-dev] Alternative bytecode sets demo request

2017-12-04 Thread Eliot Miranda
Hi Ben, > On Dec 4, 2017, at 4:17 AM, Ben Coman wrote: > >> On 4 December 2017 at 10:48, Eliot Miranda wrote: >> Hi Ben, >> >>> On Sun, Dec 3, 2017 at 6:08 PM, Ben Coman wrote: >>> >>> I'm shooting in the dark here since

Re: [Pharo-dev] Alternative bytecode sets demo request

2017-12-04 Thread Ben Coman
On 4 December 2017 at 10:48, Eliot Miranda wrote: > Hi Ben, > > On Sun, Dec 3, 2017 at 6:08 PM, Ben Coman wrote: >> >> I'm shooting in the dark here since its a bit hard to grasp... >> a. The implications of support alternative bytecode sets >>

Re: [Pharo-dev] Alternative bytecode sets demo request

2017-12-03 Thread Clément Bera
To use the alternate bytecode set in Pharo 7 use: CompilationContext bytecodeBackend: EncoderForSistaV1. OpalCompiler recompileAll. based on: https://clementbera.wordpress.com/2017/07/19/sista-open-alpha-release/ Currently in Pharo SqueakV3PlusClosure and SistaV1 are installed in

Re: [Pharo-dev] Alternative bytecode sets demo request

2017-12-03 Thread Eliot Miranda
Hi Ben, On Sun, Dec 3, 2017 at 6:08 PM, Ben Coman wrote: > I'm shooting in the dark here since its a bit hard to grasp... > a. The implications of support alternative bytecode sets > * Do the alternative bytecode sets run in parallel to normal Pharo > bytecodes? >

[Pharo-dev] Alternative bytecode sets demo request

2017-12-03 Thread Ben Coman
I'm shooting in the dark here since its a bit hard to grasp... a. The implications of support alternative bytecode sets * Do the alternative bytecode sets run in parallel to normal Pharo bytecodes? * Can the bytecode sets be loaded adhoc/dynamically into an Image? or only compiled