On 27 March 2017 at 01:37, Ben Coman wrote:
> On Mon, Mar 27, 2017 at 5:25 AM, Alistair Grant wrote:
>> Trying to use the VM produces:
>>
>> THERE_BE_DRAGONS_HERE
>> Your VM is too old for this image. Please download the latest VM.
>> 26 March 2017 10:54:36.099174 pm
>
> Last night I built the 64
Thanks for tips to external Date/Time implementation.
I implemented custom #= and #< methods in Date class as extension to solve my
issue.
It's sad a little, that base Date/Time classes is not enough and external libs
existed.
pf
>
> > On 26 Mar 2017, at 21:56, Stephane Ducasse wrote:
> >
On Mon, Mar 27, 2017 at 5:25 AM, Alistair Grant wrote:
> Trying to use the VM produces:
>
> THERE_BE_DRAGONS_HERE
> Your VM is too old for this image. Please download the latest VM.
> 26 March 2017 10:54:36.099174 pm
Last night I built the 64-bit pharo-vm on OSX
and then trying to run 60451-64.im
Hi Esteban & Ben,
On 26 March 2017 at 10:49, Esteban Lorenzano wrote:
>
>> On 26 Mar 2017, at 09:10, Alistair Grant wrote:
>> I haven't used travis, but it looks like it is defining a number of
>> environment variables, e.g. ARCH, FLAVOR, SRC_ARCH, HEARTBEAT. If I
>> want the 32 bit linux threa
> On 26 Mar 2017, at 21:56, Stephane Ducasse wrote:
>
> Did you check the Zn counterpart because I know that some parts are much
> better.
> But I do not have them at hand.
You mean ZTimestamp (but it is not a part of Zinc HTTP Components).
https://github.com/svenvc/ztimestamp
This is an UTC
Did you check the Zn counterpart because I know that some parts are much
better.
But I do not have them at hand.
Stef
On Sun, Mar 26, 2017 at 10:17 AM, Petr Fischer wrote:
> Hello,
>
> 1) when I create date on: 2017/03/20 (before Daylight Saving Time change)
> with this code:
>
> D1 := Date yea
Even "Date today" and "Date now" is created by DateAndTime.
So, due to the DateAndTime internals, one can't persist Date instance (eg. with
Fuel) and use it as exact "date/day value" for comparisons later in time (when
GST changes back and forth).
The same date value (one created before DST chan
Le 26/03/2017 à 19:21, Peter Uhnak a écrit :
On Sun, Mar 26, 2017 at 05:45:04PM +0200, Esteban Lorenzano wrote:
On 26 Mar 2017, at 15:40, Peter Uhnak wrote:
Hi,
is it possible to use UFFI and avoid crashing the image when the
called code segfaults?
In other words, can I somehow wrap the ca
Add an issue in the Voyage github repo and do a pull request to push
esteban
releasing a new version.
On Sun, Mar 26, 2017 at 1:15 PM, Norbert Hartl wrote:
> I get that same problem, too, every time I do "Software update". But never
> understood the rationale of dropping a database at this poin
On Sun, Mar 26, 2017 at 05:45:04PM +0200, Esteban Lorenzano wrote:
>
> > On 26 Mar 2017, at 15:40, Peter Uhnak wrote:
> >
> > Hi,
> >
> > is it possible to use UFFI and avoid crashing the image when the called
> > code segfaults?
> >
> > In other words, can I somehow wrap the call and throw i
On Sun, Mar 26, 2017 at 11:43 PM, Stephan Eggermont wrote:
> On 26/03/17 04:16, Pierce Ng wrote:
>>
>> On Sat, Mar 25, 2017 at 07:56:03PM +0100, Stephan Eggermont wrote:
>>>
>>> On 25/03/17 18:29, serge.stinckw...@gmail.com wrote:
Nice ! But do you have a way to automatize this process ?
On Sun, Mar 26, 2017 at 05:45:04PM +0200, Esteban Lorenzano wrote:
>
> > On 26 Mar 2017, at 15:40, Peter Uhnak wrote:
> >
> > Hi,
> >
> > is it possible to use UFFI and avoid crashing the image when the called
> > code segfaults?
> >
> > In other words, can I somehow wrap the call and throw i
> Hi,
>
> is it possible to use UFFI and avoid crashing the image when the called
> code segfaults?
>
>
Yes its possible. When I was exploring the means to live code with C++ I
came to specific implementations of live coding for C++. One of them
explored a feature called "Hardware exceptions" .Hard
Big data, like the ‘cloud’, is mainly a marketing thing to sell big iron in big
datacenters. So if you’re going back to big iron anyway, might as well use
VisualGen for COBOL.
What? VisualGen is written in IBM Smalltalk? Just don’t tell anyone, they’ll
never guess.
Andrew
On 2017-03-26, 1
> On 26 Mar 2017, at 15:40, Peter Uhnak wrote:
>
> Hi,
>
> is it possible to use UFFI and avoid crashing the image when the called code
> segfaults?
>
> In other words, can I somehow wrap the call and throw in-image
> Exception/Error on failure instead of the whole thing crashing?
that’s no
On 26/03/17 04:16, Pierce Ng wrote:
On Sat, Mar 25, 2017 at 07:56:03PM +0100, Stephan Eggermont wrote:
On 25/03/17 18:29, serge.stinckw...@gmail.com wrote:
Nice ! But do you have a way to automatize this process ? ;-)
How difficult can it be? We did it 18 years ago in java & delphi :)
I was
Hi,
is it possible to use UFFI and avoid crashing the image when the called code
segfaults?
In other words, can I somehow wrap the call and throw in-image Exception/Error
on failure instead of the whole thing crashing?
Or is the only way to do that have the called thing running as a separate a
On Sun, Mar 26, 2017 at 3:10 PM, Alistair Grant wrote:
> On 26 March 2017 at 04:09, Pierce Ng wrote:
>> On Sat, Mar 25, 2017 at 07:29:29PM +0100, Alistair Grant wrote:
>>> make[3]: *** No rule to make target
>>> '/usr/lib/i386-linux-gnu/libssl.so', needed by 'libgit2.so.0.23.0'.
>>
>> Sorry, also
Indeed. It was just I was in the middle of something.
Le 25/03/2017 à 19:10, Stephane Ducasse a écrit :
> you should think to move to Pharo 50. We closed around 1500 issues between
> pharo 40 and pharo 50 and the same amount between pharo 50 and pharo 60.
> Pharo 50 is really stable and working
I get that same problem, too, every time I do "Software update". But never
understood the rationale of dropping a database at this point. I think we
should remove this line
Norbert
> Am 25.03.2017 um 22:04 schrieb Hilaire :
>
> ah yeah, I wrote an internal durty hack to get it rolling
>
> cle
Date>>year:month:day: (respectively Date>>#starting:) is using DateAndTime to
specify the start, and DateAndTime will of course differ.
To me it seems like someone was reusing implementation; because Date normally
shouldn't have/care about time information, and yet it subclasses from Timespan
c
> On 26 Mar 2017, at 09:10, Alistair Grant wrote:
>
> On 26 March 2017 at 04:09, Pierce Ng wrote:
>> On Sat, Mar 25, 2017 at 07:29:29PM +0100, Alistair Grant wrote:
>>> make[3]: *** No rule to make target
>>> '/usr/lib/i386-linux-gnu/libssl.so', needed by 'libgit2.so.0.23.0'.
>>
>> Sorry, also
Hello,
1) when I create date on: 2017/03/20 (before Daylight Saving Time change) with
this code:
D1 := Date year: 2017 month: 3 day: 26.
Date object is created with instvars:
start: 2017-03-26T00:00:00+01:00
duration: 1:00:00:00
2) when I create same Date instance with the same code on/after:
On 26 March 2017 at 04:09, Pierce Ng wrote:
> On Sat, Mar 25, 2017 at 07:29:29PM +0100, Alistair Grant wrote:
>> make[3]: *** No rule to make target
>> '/usr/lib/i386-linux-gnu/libssl.so', needed by 'libgit2.so.0.23.0'.
>
> Sorry, also
>
> % sudo apt-get install libssl-dev:i386
Thanks, Pierce.
24 matches
Mail list logo
