>
>
> In Ruby it is dead simple:
> str[/\[(.*)\]/,1].hex # "=> 37" , or .to_i(16)
>
and dead unreadable
Pharo way is both dead simple and dead readable
str:= ' Temperature 0 37C (98F) [0x25] (TMPIN0)'.
('16r',(text copyWithRegex: '(.*\[0x)|(\].*)' matchesReplacedWith: ''))
asNu
On Sun, 15 Jan 2017 14:53:31 +0100, Peter Uhnak wrote:
I find these endless git vs monticello discussions confusing and
pointless.
+ 1
:)
Maybe we can hang Q&A list somewhere on pharo website to point to?
Because git is getting increased traction in Pharo, so the same
questions an
tx this one was easy :)
On Mon, 16 Jan 2017 21:56:48 +0100, sergio ruiz
wrote:
Of all the great things i have seen added to pharo over the past years,
the absolute coolest i have yet seen is the addition of a hotkey
sequence for “Save Image”..
Thank you guys so much!
peace,
ser
Pay attention that Singleton should not be about access but time.
If you can by adding on instance variable avoid to need a singleton then
it means that it was not a singleton.
A singleton is often:
you **CANNOT** have two instances at the same time.
Many people do not use well singl
Hi doru
where do we see it?
Stef
On Fri, 20 Jan 2017 16:57:51 +0100, Tudor Girba
wrote:
Hi,
When you have questions like these, you can also use the built-in
debugging facilities. For example, in your case, you can see that the
#any parser consumed everything like this:
Cheers,
>* I have to manually remove the 0x, even though it is a very common way of
>expressing hex numbers
Adding a few lines to NumberParser>>#nextNumber enables it to parse 0x...
---
((sourceStream peekFor: $r)) ifTrue: ["r"
...
]
ifFalse: [
(sourceStr
On Sat, Jan 21, 2017 at 11:19:24AM +0100, stepharong wrote:
> Pay attention that Singleton should not be about access but time.
>
> If you can by adding on instance variable avoid to need a singleton
> then it means that it was not a singleton.
>
> A singleton is often:
>you **CANNOT** ha
> On 21 Jan 2017, at 11:59, Peter Uhnak wrote:
>
> On Sat, Jan 21, 2017 at 11:19:24AM +0100, stepharong wrote:
>> Pay attention that Singleton should not be about access but time.
>>
>> If you can by adding on instance variable avoid to need a singleton
>> then it means that it was not a single
Hi.
2017-01-20 16:15 GMT+01:00 Peter Uhnak :
> In Ruby it is dead simple:
> str[/\[(.*)\]/,1].hex # "=> 37"
>
I always wondering when people think it is dead simple.
I use streams for such cases. It is logical, readable and dead simple
approach without crappy syntax. And with Xtreams library it
Nice one. str:= --> text :=
On Sat, Jan 21, 2017 at 10:07 AM, Dimitris Chloupis
wrote:
>
>> In Ruby it is dead simple:
>> str[/\[(.*)\]/,1].hex # "=> 37" , or .to_i(16)
>>
>
> and dead unreadable
>
> Pharo way is both dead simple and dead readable
>
> str:= ' Temperature 0 37C (9
On Sat, Jan 21, 2017 at 02:01:59PM +0100, Denis Kudriashov wrote:
> Hi.
>
> 2017-01-20 16:15 GMT+01:00 Peter Uhnak :
>
> > In Ruby it is dead simple:
> > str[/\[(.*)\]/,1].hex # "=> 37"
> >
>
> I always wondering when people think it is dead simple.
> I use streams for such cases. It is logical,
On Sat, Jan 21, 2017 at 1:22 AM, Bernhard Pieber
wrote:
> Hi Johan,
>
> Thank you for your detailed answer. See below.
> > Am 20.01.2017 um 10:12 schrieb Johan Brichau :
> >
> > imho, it’s better practice to detect too large file upload in your app
> on the client side, i.e. before your user has
I collected some content about that and wanted to do something about it
but, yeah, it got on the backburner.
This is currently just the extract of the package comment or something like
that.
https://github.com/philippeback/xstreamsdoc
Phil
On Sat, Jan 21, 2017 at 3:08 PM, Peter Uhnak wrote:
>
Agree on the hook. However the super class are not mine. Not an ideal
situation
Le 21/01/2017 à 11:19, stepharong a écrit :
> No and I'm happy that this is like that.
> I think that it means that you need to create special hooks in the super
> superclass.
--
Dr. Geo
http://drgeo.eu
Yep, it is the first situation I face where I need it in 10 years of
Smalltalk/Pharo. Otherwise I will refactor super class package, may be I
should
Le 21/01/2017 à 11:19, stepharong a écrit :
> pay attention and to not use it. It is evil to use that in plain domain
> code.
--
Dr. Geo
http://drg
Hi,
The inspector shows the PPFailure, and the Debug View presentation of PPFailure
shows you the paths the parser tried.
star produces a PPPossessiveRepeatingParser, and selecting it shows that it
matched all three characters: they are selected in the bottom pane which shows
the input string.
I use PetitParser for this purpose.
It provides:
- an incremental way to build a parser especially when you use its bounded sea
abilities,
- a way to debug problems, and
- a reasonably readable outcome that can be extended to a more complicated
parser.
For example, in your case, you can use:
s
2017-01-21 17:09 GMT+01:00 p...@highoctane.be :
> I collected some content about that and wanted to do something about it
> but, yeah, it got on the backburner.
>
> This is currently just the extract of the package comment or something
> like that.
>
> https://github.com/philippeback/xstreamsdoc
>
Out of curiosity, wouldn't it be better to temporarily duplicate the code in
your class and talk with the upstream owner? (That would be my usual approach.)
Peter
On Sat, Jan 21, 2017 at 06:04:12PM +0100, Hilaire wrote:
> Agree on the hook. However the super class are not mine. Not an ideal
> s
On Sat, Jan 21, 2017 at 07:09:19PM +0100, Denis Kudriashov wrote:
> 2017-01-21 17:09 GMT+01:00 p...@highoctane.be :
>
> > I collected some content about that and wanted to do something about it
> > but, yeah, it got on the backburner.
> >
> > This is currently just the extract of the package comme
--- Begin Message ---
Hi Hilaire,
I had this once, too. No time to refactor or rethink my subclass structure.
Now I am wondering what you guys are meaning by "hooks"?
Something like this? A ClassExtension?
SuperSuperClass
- methodIWantToReach
- myExtendedMethod
^self methodIWan
Actually the things I snatched are from there.
Phil
On Sat, Jan 21, 2017 at 7:19 PM, Peter Uhnak wrote:
> On Sat, Jan 21, 2017 at 07:09:19PM +0100, Denis Kudriashov wrote:
> > 2017-01-21 17:09 GMT+01:00 p...@highoctane.be :
> >
> > > I collected some content about that and wanted to do somethin
There is also this
https://github.com/SquareBracketAssociates/PharoLimbo/tree/master/Xtreams
On Sat, Jan 21, 2017 at 3:08 PM, Peter Uhnak wrote:
> On Sat, Jan 21, 2017 at 02:01:59PM +0100, Denis Kudriashov wrote:
> > Hi.
> >
> > 2017-01-20 16:15 GMT+01:00 Peter Uhnak :
> >
> > > In Ruby it is
Yes I should finish to convert everything.
I hope that in Pharo 70 we will be able add Xtream like library and remove
the old stream
but this is large task.
stef
On Sat, 21 Jan 2017 21:06:34 +0100, p...@highoctane.be
wrote:
There is also this
https://github.com/SquareBracketAssociates
tx
On Sat, 21 Jan 2017 18:09:32 +0100, Tudor Girba
wrote:
Hi,
The inspector shows the PPFailure, and the Debug View presentation of
PPFailure shows you the paths the parser tried.
star produces a PPPossessiveRepeatingParser, and selecting it shows that
it matched all three characters
yes, something like factoring out in its own method a chunk of code in
super super method I want to access from my subclass.
Le 21/01/2017 à 19:32, Sebastian Heidbrink via Pharo-users a écrit :
> Now I am wondering what you guys are meaning by "hooks"?
--
Dr. Geo
http://drgeo.eu
Yes I like your blog entry.
But my point is orthogonal :)
On Sat, Jan 21, 2017 at 11:19:24AM +0100, stepharong wrote:
Pay attention that Singleton should not be about access but time.
If you can by adding on instance variable avoid to need a singleton
then it means that it was not a singleton.
Ah, I now see my googing issue, because apparently noone knows whether the name
is Xtreams or Xstreams
If I google 'Pharo Xtreams' (which is the correct name it seems) I get fuckall,
but if I google 'Pharo Xstreams' I get the link as second result, just because
someone misspelled the filename. -
Worst than that :) In theory I can refactor the super code and commit,
but SmalltalkHub does not let me commit even I have RW access... So I
have to knock at the Philippe's or Masashi's door so they can commit it
for me. It's annoying to bother busy people. Anyway enough small talk ;)
Le 21/01/201
Dtto as above. Readability was never a question. And if it was, then you
> just doubled the regex complexity, and made the code more confusing by
> turning the problem upside down, due to the limited API.
Complaining about the compact syntax makes as much sense as complaining
> that `1+2` is too
Reability: the more you read a language, the more you can read it.
And saying Python is super readable can have a look at how BSON is dealt
with in the MongoDB driver.
https://github.com/mongodb/mongo-python-driver/tree/master/bson
Now go check the same in MongoTalk. Where you can actually unders
31 matches
Mail list logo
