[squeak-dev] Re: [Pharo-dev] Xtreams in Pharo 3

Nicolas Cellier nicolas.cellier.aka.nice at gmail.com
Tue Nov 19 22:50:08 UTC 2013


For the OpalCompiler support, I have simply added the compiler method in
Xtreams-Parsing because it does not conflict with anything else, I have the
feeling that this is bearable...
I have also added a NotFoundError subclass of NotFound in Xtreams-support.
It's not ideal. That also means that bleeding-edge will not load in Squeak
4.4 or older, and maybe not elder version of Pharo...
Maybe I could have changed NotFoundError reference into NotFound?
In the future, or if we really want a bleding edge in elder images, we may
have to fork the Xtreams-support, but as long as we can, it's better to
avoid it.


2013/11/19 Sven Van Caekenberghe <sven at stfx.eu>

>
> On 18 Nov 2013, at 22:33, Nicolas Cellier <
> nicolas.cellier.aka.nice at gmail.com> wrote:
>
> > Ah, NotFoundError is also undeclared in Squeak, it is the VisualWorks
> class name.
> > It could go into Xtreams-Support...
>
> OK, are you going to check this in, or should I ?
>
> How are we going to deal with platform specific stuff (like the Opal
> compiler switch) ?
>
> Sven
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20131119/d44c597c/attachment.htm


More information about the Squeak-dev mailing list