[Pharo-project] Bug in Pharo compiler?

Henrik Sperre Johansen henrik.s.johansen at veloxit.no
Wed Oct 6 17:18:10 EDT 2010

  Hit the button a bit fast there...

On 06.10.2010 23:13, Henrik Sperre Johansen wrote:
> On 06.10.2010 22:56, James Ladd wrote:
>> Hi All,
>> Currently im running the Redline Smalltalk compiler 
>> (http://redline.st) over the Pharo source
>> to make sure that it is compatible with Pharo.
>> What I noticed while compiling the class BitBlt is that an instance 
>> variable is also used as
>> a method argument name!
>> If you try and do this with the environment you get a "name already 
>> defined" error, yet
>> it is in the source.
>> Not sure what to do about it?
>> Rgs, James.
> The compiler has been changed to be more strict about shadowing inst 
> vars, but code which has not been since the change was made may still 
> exist.
... which has not been altered since the change...
> Submit a bug to the tracker mentioning the affected method, and it 
> will be fixed.
Which would be to rename the method argument name, by the way.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20101006/b767b112/attachment-0001.html>

More information about the Pharo-dev mailing list