Hi
2018-07-17 9:55 GMT+01:00 teso...@gmail.com :
> Hi Torsten,
>the problem is defining the behavior expected from the set of messages:
>
> Today we have 3 (yes 3 awful) they are to keep compatibility with the
> tools, we have to continue improving them.
>
> - allSlots: returns all the
--- Begin Message ---
It would be fantastic that people try it out. It is easy to use, and is really
a big improvement over the tool set we use.
And getting feedback is important.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
teso...@gmail.com wrote
> the one that is disturbing, it is kept for
> compatibility with the old behavior
Are there enough users to justify backward compatibility if it costs a nice
API?
-
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html
Hello,
I am finally releasing an initial public version of Pharo Git Thermite, a
tool that I am developing as part of my master thesis for visualizing
Monticello and Git commits, for Pharo and Python:
GitHub Page with sources/documentation/issue tracker:
There is a new Pharo build available!
The status of the build #1127 was: FAILURE.
The Pull Request #1487 was integrated:
"22067-Duplicated-packages-in-Pharo-baselines-SUnit-and-BasicTools"
Pull request url: https://github.com/pharo-project/pharo/pull/1487
Issue Url:
Hi Pablo,
thanks for the quick answer. The attached CS would fix it ... can you have a review so we can open a bug and do a PR?
Then at least this could be integrated independent from when the tools and traits are cleaned up.
Thanks
T.
FixIndexSlottedTraits.cs
Description: Binary data
On 16 Jul 2018, at 19:46, Alistair Grant wrote:
Hi Sven & Max,
On Fri, Jul 13, 2018 at 07:59:32PM +0200, Sven Van Caekenberghe wrote:
Alistair, are you aware of the following (article/codebase) ?
https://medium.com/concerning-pharo/an-implementation-of-unicode-normalization-7c6719068f43
Hi Torsten,
the problem is defining the behavior expected from the set of messages:
Today we have 3 (yes 3 awful) they are to keep compatibility with the
tools, we have to continue improving them.
- allSlots: returns all the slots defined in the hierarchy, in the same
class and in all the
I guess I found a bug in accessing Slots using #slots in combination with
IndexedSlots and traits.
To reproduce use latest Pharo 7 (Build 1126)
First create a class with a slot, note that the slot needs to be :
Object subclass: #ClassA
slots: { IndexedSlot named: #upper }
