25 Feb
2010
25 Feb
'10
1:25 p.m.
I'm not able to tell what is the problem. It seems that the line:
string replaceAll: $ä with: $a.
is the origin of the problem.
By sending 'proceed' to this syntax error, all ends with success.
I have also another question:
If in visual works, the package contains extensions to classes that no
longer exist in Pharo, what is the solution to port it to Pharo?
2010/2/25 Tudor Girba <tudor.girba(a)gmail.com>
But what generates the error?
Cheers,
Doru
On 25 Feb 2010, at 11:29, Simon Denier wrote:
On 25 févr. 2010, at 11:09, Cyrille Delaunay
wrote:
Hello,
--
www.tudorgirba.com
"Some battles are better lost than fought."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
I'm trying to convert some packages from VW to Pharo. For that, I use the
technic described in the SCG wiki (using the squeak exporter in visual works
and then dragging the .st file in pharo). For some packages it works well.
For other, I have syntax errors (that don't really described the problem).
In these case, what is the solution ?
You have to fix the st file by hand. The syntax error (with respect to the
Pharo parser) is sometimes easy to spot, sometimes not. I think there is way
to get a better error review.
--
Simon
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev