Sean P. DeNigris wrote
MAJOR API CHANGE:
- change matcher #= to #equal: e.g. 1 should = 1 would now be written 1
should equal: 1
- update all code to use new API
Motivation: the #= magic made it impossible to store matchers in
dictionaries, and #hash was implemented to signal an error
Hi Sean:
On 29 Aug 2014, at 03:17, Sean P. DeNigris s...@clipperadams.com wrote:
Stefan Marr-3 wrote
It doesn’t look like it has public write access.
Guess the error is between chair and screen. I probably forgot to save the
change or something…
Now it should be enabled.
It may have
Stefan Marr-3 wrote
It doesn’t look like it has public write access.
Guess the error is between chair and screen. I probably forgot to save the
change or something…
Now it should be enabled.
It may have reverted during the recent sthub problems. Would you try one
more time, or add me as a
Hi Sean:
On 24 Apr 2014, at 02:49, Sean P. DeNigris s...@clipperadams.com wrote:
Stefan Marr-3 wrote
First of all, I enabled public write access on the repository.
It doesn’t look like it has public write access.
Guess the error is between chair and screen. I probably forgot to save the
Stefan Marr-3 wrote
Now it should be enabled.
Looks good, thanks!
-
Cheers,
Sean
--
View this message in context:
http://forum.world.st/Phexample-API-Change-Proposal-was-Phexample-Image-Destroying-Bug-tp4755787p4756229.html
Sent from the Pharo Smalltalk Developers mailing list archive at
Stefan Marr-3 wrote
First of all, I enabled public write access on the repository.
It doesn't look like it has public write access. Notice the difference
compared to the Pharo Inbox:
http://forum.world.st/file/n4756130/Phexample.png
vs.
http://forum.world.st/file/n4756130/Pharo_Inbox.png
Reverting EyeInspector#updateList revealed the error when Phexample is used
in latest Pharo 3.0...
PhexMatcher uses #= as part of it's DSL e.g. 1 should = 1. Because it
doesn't respond normally to #=, #hash is implemented to signal an error
(self error: 'Don''t put a matcher into a dictionary. It
Hi Sean:
First of all, I enabled public write access on the repository.
While I am the admin on the project, I took it over from Niko and Adrian, and
at this point, I would consider it ‘community maintained’.
The rest inline:
On 22 Apr 2014, at 16:40, Sean P. DeNigris s...@clipperadams.com
Stefan Marr-3 wrote
Still, I will state it anyway: I don’t like the change.
I expected it to be unpopular ;)
Stefan Marr-3 wrote
So, just for the sake of argument, are there other ways?
I don't know. I'm open...
As far as making #= mean something different the first time, I think this
gets
On Tue, Apr 22, 2014 at 7:26 PM, Sean P. DeNigris s...@clipperadams.comwrote:
Stefan Marr-3 wrote
Still, I will state it anyway: I don’t like the change.
I expected it to be unpopular ;)
Stefan Marr-3 wrote
So, just for the sake of argument, are there other ways?
I don't know. I'm
10 matches
Mail list logo