--- Begin Message ---
+1
> On Jan 2, 2020, at 9:24 PM, Pierce Ng wrote:
>
> On Thu, Jan 02, 2020 at 12:56:55PM -0600, Sean P. DeNigris wrote:
>> bugs seem to be
>> more severe and difficult to diagnose, so we'll see how it goes as FFI use
>> becomes more and more common...
>
> There's a saying
On Thu, Jan 02, 2020 at 12:56:55PM -0600, Sean P. DeNigris wrote:
> bugs seem to be
> more severe and difficult to diagnose, so we'll see how it goes as FFI use
> becomes more and more common...
There's a saying about (aspects of) building software which source I
cannot recall:
If it hurts, do
Hi All,
I'm getting an inscrutable error when using the regular zeroconf (curl
https://get.pharo.org | bash) and trying to run the resulting ./pharo
script:
```
ioLoadModule(/home/egade/ui-test-1/ui/test/pharo-vm/lib/pharo/5.0-201901051900/libgit2.so):
libz.so.1: cannot open shared object file:
On Thu, Jan 2, 2020 at 3:47 PM Sean P. DeNigris wrote:
>
> Tim Mackinnon wrote
> > I’m getting the impression that ffi is getting very easy these days and
> > maybe we should use it more to focus on “other” things... This said, many
> > of our nastiest bugs...
>
> That said, as you pointed out, bu
Tim Mackinnon wrote
> I’m getting the impression that ffi is getting very easy these days and
> maybe we should use it more to focus on “other” things... This said, many
> of our nastiest bugs...
While I dream of a world where everything is in-image as pure Smalltalk,
given the reality of limited
That makes sense - I’m getting the impression that ffi is getting very easy
these days and maybe we should use it more to focus on “other” things.
It does complicate deployment a bit - but if you’re server/cloud based then
that’s less of an issue anyway .
This said, many of our nastiest bugs s
On Fri, 3 Jan 2020 at 00:41, Roelof Wobben wrote:
> Hello Ben.
>
> That was a error . There schould be a caret for it. Im talking about the
> solution method.
>
> No, I cannot clean the in part because it is used in the process* methods
>
But its not. Your statement would be true if your proc
Pierce Ng-3 wrote
> Also I saw hoedown's wiki page on bindings and thought I'd put Smalltalk
> on the map there.
Great!
-
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
Pharo Smalltalk Users mailing list wrote
>I made some changes. Is this better or are there still some code
> smells.
I don't have time for an in-depth review, but I skimmed it and it seems
better.
-
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.htm
--- Begin Message ---
Hello Ben.
That was a error . There schould be a caret for it. Im talking
about the solution method.
No, I cannot clean the in part because it is used in the process*
methods
The processData: can also be delet
Hi Roelof,
I presume its working since you only asked for code smells.
It looks pretty good to me with methods generally being small and doing one
thing.
The way your class-side-method "IntComputer class >> solution" just creates
an instance and sends #process is good.
I'm a little curious that i
--- Begin Message ---
Op 1-1-2020 om 17:27 schreef Roelof
Wobben via Pharo-users:
Hello,
I made some changes. Is this better or are there still some code
smells.
Code :
https://github.com/rwobben/intComputer/blob/master/AOC%202019/IntCompu
12 matches
Mail list logo
