Hi Offray,
I have not had a look at your code, but I have the impression that the tricky
part is getting the data. I guess you can open a repository, get all the files,
and get the data from a .mcz file. When you click on the ‘Browse’ button in the
Monticello browser, you can see all the classe
Phil,
I mixed up the books. It "Fundamentals of Smalltalk Programming
Technique, Volume 1" by "Andres Valloud". Just checked it.
http://www.lulu.com/shop/andres-valloud/fundamentals-of-smalltalk-programming-technique-volume-1/paperback/product-5299835.html
CU,
Udo
On 23.09.14 16:05, Udo Sc
> Yes I do, but you also know (it was clear from the article) that you
> learn a lot yourself from writing something for public consumption.
> Most people underestimate how powerful that is.
True indeed - sorting my thoughts to be able to write them down in a
coherent way for public consumption r
On 23 Sep 2014, at 21:00, Udo Schneider wrote:
> Hi Sven,
>
> thanks for the feedback.
>
> > Keep that kind of stuff coming, it is very helpful.
> I'll try to. It just always takes so long to write stuff. But I think you
> know that, don't you? :-)
Yes I do, but you also know (it was clear f
Hi Sven,
thanks for the feedback.
> Keep that kind of stuff coming, it is very helpful.
I'll try to. It just always takes so long to write stuff. But I think
you know that, don't you? :-)
CU,
Udo
On 23.09.14 16:00, Sven Van Caekenberghe wrote:
Hi Udo,
This is really an excellent article:
> I reviewed a few techniques for implementing internal / embeddel DSLs in
> a host language and I didn't saw this one :)
IMHO it's a nice tool to know about. Only for specific use cases but
still useful.
CU,
Udo
On 23.09.14 09:06, Thierry Goubier wrote:
Thanks Udo;
I reviewed a few techni
2014-09-23 15:57 GMT+02:00 Udo Schneider :
> > Confirmed in even a better way: given how convoluted and hacky is
> > writing a full Python Parser, it is probably not even a Context Free
> > Grammar.
> Let's agree on the fact that you'll be able to parse it using Context
> Sensitive Grammar (Type 1
Thank you your examples work for me as well, and it’s pretty fast drawing !
Annick
Le 23 sept. 2014 à 01:04, p...@highoctane.be a écrit :
>
>
> I've got the 32 bit ones. I checked.
>
> Nicolas got it working, I'll check.
>
> Phil
>
>
>
> On Tue, Sep 23, 2014 at 12:32 AM, Casimiro de Almeid
Phil,
If I remember correctly one of Andres Valloud's books has some more
information on Boolean (logic) and Smalltalk. I think it was "A
Mentoring Course on Smalltalk" [1]. Definitely worth a read!!
CU,
Udo
[1]
http://www.lulu.com/shop/andres-valloud/a-mentoring-course-on-smalltalk/paper
Hi Udo,
This is really an excellent article: I enjoyed reading it a lot.
It is well written, has lots of relevant code examples and a nice pace, but
above all it is really interesting.
Thanks a lot.
Keep that kind of stuff coming, it is very helpful.
Sven
On 23 Sep 2014, at 01:48, Udo Schnei
> Confirmed in even a better way: given how convoluted and hacky is
> writing a full Python Parser, it is probably not even a Context Free
> Grammar.
Let's agree on the fact that you'll be able to parse it using Context
Sensitive Grammar (Type 1) for sure ... and if you're very lucky Context
Fre
Le 23/09/2014 14:09, Damien Cassou a écrit :
> I recently read documents about utf-8 encoding. In all of them, the
> author says that pathnames should be kept as is because you never know
> which encoding the filesystem uses. So, a filename should probably be
> a bytearray.
yes, but a #é should b
damn you guys speak in a language I am not aware of :D Looks like I have
reading to do.
Anyway regex worked fin for converting pharo messages to python method
calls and assignment / reading variables . Regex was actually quite simple
to learn.
Now for classes I dont know if RBParser would be an o
2014-09-23 13:57 GMT+02:00 Udo Schneider :
> > yeap noway I compare Regex with PettitParser. I will probably give a
> > PettitParser a try, because I try to parse Pharo syntax to Python, I
> > want now to parse Pharo classes to python class and that will be a
> > nightmare with regex, so time to g
On Mon, Sep 22, 2014 at 10:07 PM, Hilaire wrote:
> However font path seems ok:
> File @ /home/hilaire/Téléchargements/DrGeo.app/Contents/Resources.
> Inspecting this path, it looks like 'Téléchargements' is 8 bits, but it
> should be utf-8, right?
I recently read documents about utf-8 encoding.
Thx for this!
I'd say that the material is worthy of inclusion into a bool chapter.
Phil
Le 23 sept. 2014 12:51, "Udo Schneider" a
écrit :
> Phil,
>
> I'd say that's an implementation of the "Material implication"[1] operator
> from Propositional calculus.
>
> You can write it as
>
> P -> Q
>
>
> yeap noway I compare Regex with PettitParser. I will probably give a
> PettitParser a try, because I try to parse Pharo syntax to Python, I
> want now to parse Pharo classes to python class and that will be a
> nightmare with regex, so time to give PettitParser a serious try.
Without wanting to
2014-09-23 13:35 GMT+02:00 kilon alios :
> yeap noway I compare Regex with PettitParser. I will probably give a
> PettitParser a try, because I try to parse Pharo syntax to Python, I want
> now to parse Pharo classes to python class and that will be a nightmare
> with regex, so time to give Pettit
And with FFI and Alien ? Do FFI Alien and NativeBoost share the same libraries ?
Le 22 sept. 2014 à 21:19, p...@highoctane.be a écrit :
> NativeBoost has loadModule: aModuleName which should do the trick.
>
> Phil
>
yeap noway I compare Regex with PettitParser. I will probably give a
PettitParser a try, because I try to parse Pharo syntax to Python, I want
now to parse Pharo classes to python class and that will be a nightmare
with regex, so time to give PettitParser a serious try.
On Tue, Sep 23, 2014 at 1:1
Phil,
I'd say that's an implementation of the "Material implication"[1]
operator from Propositional calculus.
You can write it as
P -> Q
and read it as "P implies Q" or (not 100% correct) "if P (is true) then
Q (is true)".
Let's take a look at the truth table:
P | Q | P -> Q
---+---+---
On 23 Sep 2014, at 6:28 , Offray Vladimir Luna Cárdenas
wrote:
> Hi :-),
>
> A small answer to myself that can be useful is someone find this thread:
>
> I have seen some post on Internet about CR and LF issues on Pharo Smalltalk,
> like this:
>
> [1]
> http://stackoverflow.com/questions/1
> I have not used PettitParser yet, looks powerful but I find it a bit
> weird in design. On the other hand regex is quite ugly and understanding
> complex regex a pain.
I normally encounter two issues with RegExps:
1) The syntax between different apps/libs/frameworks differs sligtly.
Esp. for c
Offray Vladimir Luna Cárdenas wrote:
Hi :-),
A small answer to myself that can be useful is someone find this thread:
I have seen some post on Internet about CR and LF issues on Pharo
Smalltalk, like this:
[1]
http://stackoverflow.com/questions/11739548/how-to-correctly-decode-text-files-fr
On Tue, Sep 23, 2014 at 10:15 AM, kilon alios wrote:
> it reminds a lot of Kent's Beck Smalltalk Practice Patterns where it
> removes all ifs and replaces them with regular unary messages . It is
> definitely an elegant way of coding making the code just flow.
>
> I have not used PettitParser yet
Cool article & technique indeed. Ah Smalltalk, where were you all those
years ;-)
Speaking of PetitParser, which is excellent indeed, there is this #==>
method in Boolean.
PetitParser uses that a lot. I can use the thing but do not really grasps
how it works.
Now, the method comment says:
Boole
MarkupBuilder in Groovy uses similar logic #doesNotUnderstand: .. but not
debug capable ..!..
On Tue, Sep 23, 2014 at 1:45 PM, kilon alios wrote:
> it reminds a lot of Kent's Beck Smalltalk Practice Patterns where it
> removes all ifs and replaces them with regular unary messages . It is
> defi
it reminds a lot of Kent's Beck Smalltalk Practice Patterns where it
removes all ifs and replaces them with regular unary messages . It is
definitely an elegant way of coding making the code just flow.
I have not used PettitParser yet, looks powerful but I find it a bit weird
in design. On the oth
> just as it is black magic for me now :D
The nice thing about this approach is the fact that it "just" piggybacks
the normal Smalltalk message sending. So you can step through it using
the Debugger - it's Smalltalk all the way down.
I still remember my first shock when (having no formal backg
just as it is black magic for me now :D
At least I get the general feeling. I am new to parsing too, so far I have
only played with regex parsing. Not the most smalltalkish way but it works
well so far.
On Tue, Sep 23, 2014 at 9:39 AM, Udo Schneider wrote:
> Hi Estaban,
>
> I think the first ti
On 23.09.14 02:27, Ben Coman wrote:
Very nice write up. Fairly straight forward to follow but not something
I could have done from scratch. Nice to have a recipe for it. Thanks
One spelling mistake...
> This will give es enough clues
This will give us enough clues
Thanks for the feedback -
Thanks Udo;
I reviewed a few techniques for implementing internal / embeddel DSLs in a
host language and I didn't saw this one :)
Thierry
2014-09-23 1:48 GMT+02:00 Udo Schneider :
> All,
>
> I just finished a blog entry. It shows how to use Smalltalk blocks as
> parsers/translators. E.g. transl
32 matches
Mail list logo
