Smalltalk › Squeak › Squeak - Dev

[squeak-dev] [seaBreeze-mailinglist] Porting to Squeak

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

1 message

Emilio Oca

[squeak-dev] [seaBreeze-mailinglist] Porting to Squeak

Hi Magnus,

I am interested on this issue but as I have no previous experience on
porting something that should be maintained at both ends, and I am
pretty ignorant on web issues; I just started to use it on VW for a
while.

But I'll be glad to help.

The "ifNotNil: [:p | p doSomething] should have no parameters" is a
known issue, discussed several times on the squeak list, let me search
a bit.

I think that SmaCC works ok on squeak. It shouldn't be any problem
using the Squeak Smacc port. The underscore char is used instead of
:= , so is an illegal char at the beginning of a method. But I think
there is a configurable preference on this.

I am cross posting to the squeak list, may be more help is available there.

Looking the way the seaside packages are maintained for inter-dialect
portability may be a good idea.

Cheers.

Emilio

- Hide quoted text -

On 11/12/08, Magnus Schwarz <[hidden email]> wrote:

> As nobody from the Squeak community did it by now and Gerhard Obermann
> "complained" ;) that there is no Monticello version of seaBreeze I
> decided to give it a try and port seaBreeze to Squeak.
>
> Main Problem was/is that I am used to work with Visualworks and Squeak
> is somewhat different ;)
>
> I managed to load a lot of stuff into a Pier one-click image (decided to
> use this because it should have the Seaside stuff already loaded) but
> ran into some obstacles where an experienced Squeaker might help me:
>
> - I had many methods using "ifNotNil: [:p | p doSomething]" where Squeak
> complained that the block should have no parameters - I changed the
> implementation in Squeak so that it should work but it still complained
> (and did not compile)
> - The CSSParser was built with SmaCC which generates lots of methods
> with underscores in it; now Squeak complains about the underscores but I
> do not really understand what the problem is
>
> Biggest problem seemed to be the use of SXOR - we might make porting
> much easier by deciding to drop this and use LiteralArrays (or whatever)
> in seaBreeze ...
>
> Magnus
>
> --
> Magnus Schwarz * certified Scrum Master / Smalltalk architect * mailto:[hidden email]
> phone:+49 231 97599-0 * fax:+49 231 97599-20