I'm not sure that the advice on method comments is as good as it could be.
Consider Point >>
setX: xValue setY: yValue
x := xValue.
y := yValue
It is pretty obvious what this does, and if I'm reading chapter 4 correctly
the advice is that it doesn't need a comment. But it does: why DOESN'T
On naming protocols: it would be nice to have clear guidance about
when to use '-ion' and when to use '-ing'. In my own code I've been
using '-ing' except for a few traditional categories like
'instance creation'. One reason for this was that I didn't want to
keep on re-deciding "is it
On Mon, 31 Dec 2018 at 19:34, Sven Van Caekenberghe wrote:
> Hi,
>
> I created a new release of P3, the modern, lean and mean PostgreSQL client
> for Pharo.
>
> https://github.com/svenvc/P3
>
> Version 1.1 contains the following changes:
>
> - added support for Postgres Extended Query protocol
Hi Doru,
On 29/12/18 15:50, Tudor Girba wrote:
> Hi,
>
> Thanks for the link. For some strange reason, I do not see the linked email
> in my inbox.
It was also absent from the web archives of the Pharo mailing list and,
as I'm not subscribed to Pharo-Dev I always get a warning about a
rejected
Konrad,
On 31/12/18 8:59, Konrad Hinsen via Pharo-users wrote:
>
> Thanks to everyone who replied - the sum of the answers is actually a
> lot more useful than each one individually, as each one points to a part
> of the puzzle that Pharo is (for me, at least, after roughly one month
> of use).
--- Begin Message ---
Thanks to everyone who replied - the sum of the answers is actually a
lot more useful than each one individually, as each one points to a part
of the puzzle that Pharo is (for me, at least, after roughly one month
of use).
Ben Coman writes:
> This may not be what you are
On 31/12/18 1:54 AM, Steve Quezadas wrote:
I am experimenting with pharo right now, particularly with Morphs. The
weird thing is that some morphs can have a rotation halo and others do not.
This has a "rotate halo":
bar := EllipseMorph new.
bar openInWorld.
This does not:
foo := Morph new.
Hi,
I created a new release of P3, the modern, lean and mean PostgreSQL client for
Pharo.
https://github.com/svenvc/P3
Version 1.1 contains the following changes:
- added support for Postgres Extended Query protocol (P3PreparedStatement) (thx
Jan @jvdsandt)
- added support for reading array
--- Begin Message ---
Besides, I forgot to add one comment : you should have guidelines for
protocol naming. It's not critical per se but I find it quite annoying
to look for stuff in "enumerating" when it's been put in "printing" ! loll
On 2018-12-31 03:51, Stephane Ducasse wrote:
Thanks!
