If Xtreams goes in the core of Pharo (which could be good), there should be no
compatibility layers with others platforms.
Sorry but we have too many of them and we do not want to have strings attached.
if necessary we can rename the complete library so that people can load the
real
On 23 November 2013 09:41, Stéphane Ducasse stephane.duca...@inria.fr wrote:
If Xtreams goes in the core of Pharo (which could be good), there should be
no compatibility layers with others platforms.
Sorry but we have too many of them and we do not want to have strings
attached.
if
On 23 Nov 2013, at 11:02, Frank Shearar frank.shea...@gmail.com wrote:
On 23 November 2013 09:41, Stéphane Ducasse stephane.duca...@inria.fr wrote:
If Xtreams goes in the core of Pharo (which could be good), there should be
no compatibility layers with others platforms.
Sorry but we have
If Xtreams goes in the core of Pharo (which could be good), there should be
no compatibility layers with others platforms.
Sorry but we have too many of them and we do not want to have strings
attached.
if necessary we can rename the complete library so that people can load the
real
Sven Van Caekenberghe-2 wrote
Are there version differences with the VW code, and how do you see that
evolving ?
When we looked a few years ago at ESUG in Ghent, the port was out-of-date
with the VW code. We were able to patch filetree to bring the code
round-trip to/from VW, mapping namespaces
On 20 Nov 2013, at 17:24, Sean P. DeNigris s...@clipperadams.com wrote:
Sven Van Caekenberghe-2 wrote
Are there version differences with the VW code, and how do you see that
evolving ?
When we looked a few years ago at ESUG in Ghent, the port was out-of-date
with the VW code. We were able
Sven Van Caekenberghes...@stfx.eu wrote:
On 20 Nov 2013, at 17:24, Sean P. DeNigris s...@clipperadams.com wrote:
Sven Van Caekenberghe-2 wrote
Are there version differences with the VW code, and how do you see that
evolving ?
When we looked a few years ago at ESUG in Ghent, the port
On 18 Nov 2013, at 23:12, Nicolas Cellier nicolas.cellier.aka.n...@gmail.com
wrote:
The tests pass with this hack PEGInfinityadaptToInteger: anInteger
andCompare: selector
This makes optimized inlining of timesRepeat: work.
^#( = ~= ) includes: selector
I asked Marcus for the
On 19 Nov 2013, at 17:48, Esteban Lorenzano esteba...@gmail.com wrote:
On Nov 19, 2013, at 5:40 PM, b...@openinworld.com wrote:
So does that mean that Xtreams might go into the Pharo 3 Release as a
technology preview in parallel with the existing streams, with the aim of
replacing
One more reason to look after Pharo 3 :)
Esteban A. Maringolo
2013/11/18 Sven Van Caekenberghe s...@stfx.eu:
Hi,
This evening I tried to load Nicolas Cellier’s Xtreams
(http://www.squeaksource.com/Xtreams/) into Pharo #30582. This went almost
flawless !
I went for
Ah, NotFoundError is also undeclared in Squeak, it is the VisualWorks class
name.
It could go into Xtreams-Support...
For PEG parsing test, I think you are right, this is timesRepeat:
They passed in Squeak last time I tried.
But these are advanced features not required for legacy Stream
11 matches
Mail list logo
