[Pharo-dev] Ugly smell: really long symbols/selectors

#'thisIsAVeryLongSelectorAndIfYoureHereWeHaveOnly49ImagineIHaveToWriteAllThisToArriveTo87ThenThisTo100' (ByteSymbol allInstances select: [ :e | e size > 100 ]) size => 36 (ByteSymbol allInstances select: [ :e | e size between: 50 and: 100 ]) size => 653 -- Guille Polito Research

Re: [Pharo-dev] Issue 20309 - Startup should run always in a fresh process

On Tue, Aug 15, 2017 at 3:25 PM, Ben Coman wrote: > In case any of the shutdown/startup scripts use a delay, now or in the > future, > I'd first try athighestPriority-1 to avoid influence on the > DelayScheduler. > but then Eliot's suggestion to valueUnpreemptively may

Re: [Pharo-dev] Anybody using Orca Smalltalk to JavaScript?

Hi Frank-- > > > ...especially if their sources MUST be closely connected with > > > existing Smalltalk code, which does not run in the client like > > > all the data-driven model definitions etc that I already have > > > > There is no such requirement. > > Of course, there is, actually it's an

Re: [Pharo-dev] @About posting here

Hi Frank, Le mar. 15 août 2017 à 22:11, Frank-B a écrit : > @about this forum at world.st I never use that website to interact with the mailing list. Most people I know use regular mail as me. In practice, we use that forum as conversation backup. It's also

[Pharo-dev] [Pharo 70 ] build 36 - PR 204 Improve-comment-of-SmallDictionary

https://pharo.fogbugz.com/f/cases/20091/Improve-comment-of-SmallDictionary https://github.com/pharo-project/pharo/pull/204

Re: [Pharo-dev] @Craig Latta

Hello Craig, your answer to my posting to you does not show up here and I only accidentally detected it in the flood of unwanted messages that came is. See my frustration posting above. I accidentally saw just your reply come in. This is why I am answering here to the most important points. I

Re: [Pharo-dev] @About posting here

@about this forum at world.st I have a lot of forum experience from studying "forum psychology and sociology" in three different language and in various forums run by very different software but I have never come about any system that is *nearly as crappy, sick and idiotic as this one here*: -

Re: [Pharo-dev] eventual crashes pharo vm

Thanks I will try it on my mac Sierra and report. Stef On Tue, Aug 15, 2017 at 2:59 AM, henry wrote: > Yes, here it is, in Pharo6.1, as mentioned previously. Just run the > eventual_test tests and it will exit on Ubuntu 32-bit. > > https://ufile.io/pa9ym > > Thank you,

Re: [Pharo-dev] [Pharo-users] including Pillar in Pharo image by default

> On Aug 15, 2017, at 7:25 AM, Ben Coman wrote: > > > >> On Tue, Aug 15, 2017 at 12:54 AM, Esteban A. Maringolo >> wrote: >> You hit several birds with one single mail. >> >> 2017-08-14 13:34 GMT-03:00 Tim Mackinnon : >> >

Re: [Pharo-dev] Issue 20309 - Startup should run always in a fresh process

Hi Ben, > On Aug 15, 2017, at 6:25 AM, Ben Coman wrote: > > In case any of the shutdown/startup scripts use a delay, now or in the > future, > I'd first try athighestPriority-1 to avoid influence on the > DelayScheduler. +1. In fact I'd raise it to no more than

Re: [Pharo-dev] Trying to build Mac VM - ld: library not found for -lssl

That did it. Thanks! > On Aug 14, 2017, at 7:10 AM, Nicolas Cellier > wrote: > > Reminder: i should update the readme to explain solution 2 as commented at > https://github.com/OpenSmalltalk/opensmalltalk-vm/commit/fb61b60bda7065a52d70eaf1bd0478a98d0180f7

Re: [Pharo-dev] FileSystem fix integration

Tx for the information. I will focus on 20307 then On Tue, Aug 15, 2017 at 11:07 AM, Alistair Grant wrote: > Hi Stef, > > On Tue, Aug 15, 2017 at 10:04:31AM +0200, Stephane Ducasse wrote: >> tx a lot for the summary, this is super useful :) >> I will over them later

Re: [Pharo-dev] [Pharo-users] including Pillar in Pharo image by default

On Tue, Aug 15, 2017 at 12:54 AM, Esteban A. Maringolo wrote: > You hit several birds with one single mail. > > 2017-08-14 13:34 GMT-03:00 Tim Mackinnon : > > Jimmie et al. nicely reasoned arguments - and Doru's point about > controlling > > the syntax is

Re: [Pharo-dev] New line on command line

Hey Guille, I think I found the fix. But I would like to run by you first. I want to get a review before making a PR. In the method nextPut: in ZnCrProtableWriteStream, when a new line character is sent using 'OSPlatform current lineEnding', there isn`t any statement which satisfies in this

Re: [Pharo-dev] Issue 20309 - Startup should run always in a fresh process

In case any of the shutdown/startup scripts use a delay, now or in the future, I'd first try athighestPriority-1 to avoid influence on the DelayScheduler. but then Eliot's suggestion to valueUnpreemptively may avoid that anyway. btw, what happens if an error occurs inside valueUnpreemptively?

Re: [Pharo-dev] [Vm-dev] vm crash when using rairedTo: with fractions

On Mon, Aug 14, 2017 at 4:49 PM, Tim Mackinnon wrote: > Is there a way for this to get back into 6.1 - so we can shoot for a > stable 6.x version that will last us for a year while 7.x is under > development? > > I’m not familiar with how point release are handled in Pharo, and

Re: [Pharo-dev] FileSystem fix integration

Hi Stef, On Tue, Aug 15, 2017 at 10:04:31AM +0200, Stephane Ducasse wrote: > tx a lot for the summary, this is super useful :) > I will over them later (because I must work on my new lectures :). > > Stef I've just realised that: -

Re: [Pharo-dev] New line on command line

Oh ok sure. I will try my best. :) Rajula -- View this message in context: http://forum.world.st/New-line-on-command-line-tp4960327p4961307.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Re: [Pharo-dev] FileSystem fix integration

tx a lot for the summary, this is super useful :) I will over them later (because I must work on my new lectures :). Stef On Tue, Aug 15, 2017 at 7:58 AM, Alistair Grant wrote: > Hi Stef, > > I've added the PR to fix automatic canonicalisation of path references > to the

Re: [Pharo-dev] [squeak-dev] Serializers/Encoders

To clarify, external type declarations are different that the type specification of a structure, such as an X509Certificate and its TBSCertificate. These are type applied, in similar fashion to NeoJSON, will forecite and predeterminization on both encoding and decoding sides. These type

Re: [Pharo-dev] FileSystem fix integration

Hi Stef, I've added the PR to fix automatic canonicalisation of path references to the parent directory (".."): - https://pharo.fogbugz.com/f/cases/20307/File-names-should-not-be-canonicalised-by-default - https://github.com/pharo-project/pharo/pull/206 Other open issues (to help keep