Sorry but how can we improve the situation concretely
Stef
On Wed, 14 Dec 2016 00:22:47 +0100, Andres Valloud
wrote:
Oh, ok... then the failure code isn't doing what was intended :).
On 12/13/16 15:16 , Martin McClure wrote:
On 12/13/2016 08:39 AM, Andres Valloud wrote:
I would have ex
Hi sergio
Did you find a solution to your problem?
Stef
On Tue, 13 Dec 2016 21:59:09 +0100, sergio ruiz
wrote:
Hello, all.
This question is not as much a question about smalltalk as one about
modeling in smalltalk.
I am currently writing an API using Teapot that will be serving up da
The primitive and the primitive failure code should behave the same?
On 12/18/16 2:13 , stepharong wrote:
Sorry but how can we improve the situation concretely
Stef
On Wed, 14 Dec 2016 00:22:47 +0100, Andres Valloud
wrote:
Oh, ok... then the failure code isn't doing what was intended :).
Imagine, you have some object with amount and price variables.
And you want to calculate total, put this totals to collection and
calculate grand total.
Naive implementation will be something like
total := amount * price for the first task
and something like
grandTotal := totals sum for the latter
Hi Yuri,
Long time not seeing you ! welcome back :)
Nice framework !
Esteban
> On 18 Dec 2016, at 11:45, Юрий Мироненко wrote:
>
> Imagine, you have some object with amount and price variables.
> And you want to calculate total, put this totals to collection and calculate
> grand total.
>
>
Thanks for sharing. A similar thing might be useful for dealing with
"quality" of Process Variable measurement in industrial situations -
where instruments fail from time to time.
I'm not sure of all the pros and cons, but btw an alternative to
hanging special behaviour on a method, would be to h
thanks for sharing it with us.
Now in Moose we have metrics and when a metrics value is not available
giving 0 is not the solution.
We should probably have
Value that wraps the real value for normal case and Unvalued for the case
where there is no value.
Stef
On Sun, 18 Dec 2016 11:45:3
Hi andres
I did not follow the discussion. My remark is just that a good discussion
without code for integration
does not improve Pharo and we will have people facing again the problem.
Stef
On Sun, 18 Dec 2016 11:29:11 +0100, Andres Valloud
wrote:
The primitive and the primitive failu
Thank you, Esteban!
You may believe me or not, but I dream about going to every ESUG conference
every time.
It's not framework this time, it's just small and simple package.
And it makes life much, MUCH easier when developing business applications.
2016-12-18 15:39 GMT+03:00 Esteban Lorenzano :
Sorry, I'm not sure I fully understand your idea.
It looks like trying to make another implementation of UndefinedObject, is
it?
What is the main difference between proposed MissingValue and
UndefinedObject?
It's just UndefinedObject is "too system" to intervene? Or something else?
2016-12-18 18
2016-12-18 19:43 GMT+01:00 Юрий Мироненко :
> Sorry, I'm not sure I fully understand your idea.
> It looks like trying to make another implementation of UndefinedObject, is
> it?
>
> What is the main difference between proposed MissingValue and
> UndefinedObject?
MissingValue you will set up acc
2016-12-18 20:19 GMT+01:00 Denis Kudriashov :
>
>> What is the main difference between proposed MissingValue and
>> UndefinedObject?
>
>
> MissingValue you will set up according to your business logic. While nil
> is just default value of variable which could be in your object by some
> incident,
Are you going to use relational database to store this data?
Or you goint to use image saving / object-oriented DB for persistence?
Than, can you please describe your task / domain model with more details?
Particularly:
1) Are there strong asymmetry in queries? Which kind of queries are more
frequ
On Mon, Dec 19, 2016 at 2:43 AM, Юрий Мироненко wrote:
> Sorry, I'm not sure I fully understand your idea.
> It looks like trying to make another implementation of UndefinedObject, is
> it?
Just that. But it contains only business logic.
I'm inclined to say both are the Null Object Pattern, but I
On 12/18/2016 02:29 AM, Andres Valloud wrote:
The primitive and the primitive failure code should behave the same?
You think the primitive is faulty? I haven't looked at the primitive
code, but it just fails when given a Float. From the name, I'd guess
that it's designed for a byte object. Th
Hi,
I showed Pharo to a friend and wanted to show the nice feature of fueling out
an exception and then using FLMaterializer class>>#materializeFromFileNamed: to
load it back and get a debugger up. In Pharo5 I am presented a DNU instead.
The DNU is on GTGenericStackDebugger as it doesn't unders
16 matches
Mail list logo