Thanks a lot
I think that this is a good decision.
Here is the mail of andreas mentioned by nicolas.
Folks -
I think it's time to do something about the leadingChar in Characters
that has been on the TODO list for a while. I have been looking over
this stuff for some time now, fixing things h
Oh. Why i come in magic world of Smalltalk too late (have no necessary
experience at the moment). It's job of my dream in very beautiful
place with great colleagues :)
Good luck with candidate searching.
On Mon, Mar 8, 2010 at 23:36, Stéphane Ducasse
wrote:
> Hi guys
>
> Some good news :)
> INRI
On Mon, Mar 08, 2010 at 07:47:16PM -0500, Schwab,Wilhelm K wrote:
> Hello all,
>
> Good news/bad news: I got it running again :) I have no idea what was wrong,
> nor what is right now :(
>
> A corrupt image file is not out of the question. I was having huge problems
> with Ubuntu (perhaps Lin
Hello all,
Good news/bad news: I got it running again :) I have no idea what was wrong,
nor what is right now :(
A corrupt image file is not out of the question. I was having huge problems
with Ubuntu (perhaps Linux in general??[*]) and cifs writing to windows shares.
That problem suddenly
Hello all,
I am having a sudden problem with Pharo crashing on Windows - it's quitting on
handling Seaside requests, and I'm getting **no** information. The VM pops up
the output console, writes a lot of (probably useful) information to it, and
then promptly exits.
Is there any way to get it
Hi folks. We have been working hard with Janko and we built a website for
the GSoC 2010 and for future editions!
The URL is http://gsoc2010.esug.org/
In 4 days, is the deadline to submit ESUG as mentoring organization. For
that purpose, there are several questions that we need to answer, as you
Unicode Leading Char
The default leading char is now 0 instead of 255 making Unicode - UTF
conversions stable. See also discussion at
http://lists.squeakfoundation.org/pipermail/squeak-dev/2009-August/138915.html
2010/3/8 Stéphane Ducasse :
> Hi nicolas
>
> could you give us
Hi nicolas
could you give us an executive summary of the reasoning behind this change?
Does this implies that we get Unicode by default?
and that Unicode is integrated in the table of language (replacing latin1),
so this way we do not have to check all the time is it 255?
Stef
I like all these op
Hi guys
sorry for the fact that some of you could not update anymore due to a stupid
name for package (we should check
that : space ; / cannot be put in the package name.
https://gforge.inria.fr/frs/download.php/26637/PharoCore-1.1-11254-UNSTABLE.1.zip
Stef
Hi guys
Some good news :)
INRIA-lille nord Europe ranked Pharo among the top 3 projects that will receive
support for a full time confirmed engineer.
We will know if the national level or the lab will carry the cost by mid april,
but for now the position is allocated to Pharo.
This is not the o
Many many thanks; that has been very useful for me.
Anyway I did decide change the mechanism for load and show data of my grid,
on drawing place., and now works much much more fast. Really I have poor
knowledge of different posibilities for do one thing, but I´m learning bit a
bit.
Now I will us
>
> 11254
> -
>
> - Issue 2115: Allow $- anywhere in binary selector
>
>
>
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Begin forwarded message:
> From: stephane ducasse
> Date: March 7, 2010 10:52:45 PM GMT+01:00
> To: Pharo Development
> Cc: nicolas cellier
> Subject: [update 1.1] #11253
>
> 11253
> -
>
> - Issue 2118: Let Unicode leadingChar = 0 Part 4:
>
> + cleaning package.
>
> Please no space a
Begin forwarded message:
> From: Stéphane Ducasse
> Date: March 7, 2010 6:51:30 PM GMT+01:00
> To: Pharo Development
> Subject: [update 1.1] #11252
>
>
> 11252
> -
>
> - Issue 2118: Let Unicode leadingChar = 0
> Part 3: get rid of (stopConditions at: EndOfRun) (or CrossedX)
> Replace wi
Begin forwarded message:
> From: Stéphane Ducasse
> Date: March 5, 2010 11:31:29 AM GMT+01:00
> To: Pharo Development
> Subject: [update 1.1] #11244
>
> - remove the default password squeak in the MCHttpRepository creation template
> - Introduction of tests for validating the different use ca
Begin forwarded message:
> From: Stéphane Ducasse
> Date: March 7, 2010 4:47:03 PM GMT+01:00
> To: Pharo Development
> Subject: [update 1.1] #11251
>
> 11251
> -
>
> - Issue 2119: Complete ensure blocks. Tx Andreas
> - Issue 2118: Let Unicode leadingChar = 0 (part 2)
>
> Stef
Begin forwarded message:
> From: Stéphane Ducasse
> Date: March 7, 2010 1:34:57 PM GMT+01:00
> To: Pharo Development
> Subject: [update 1.1] #11250
>
> 11250
> -
>
> - Issue 2121:Rewrite Binary Selectors Immeditely Followed By
> Negative Literal.
> rewrite all expression
Begin forwarded message:
> From: stephane ducasse
> Date: March 6, 2010 11:30:09 PM GMT+01:00
> To: Pharo Development
> Subject: [update 1.1] #11249
>
> 11249
> -
>
> - Issue 2114:Enhance SqNumberParser error handling inside Compiler.
> Tx nicolas
> - Issue 2116:Compil
> Thanks thanks thanks thanks for a refresh on that!
> Thanks!
>
> Stef
>
> On Mar 8, 2010, at 5:55 PM, Randal L. Schwartz wrote:
>
>>> "Randal" == Randal L Schwartz writes:
>>
>> Randal> And I believe some heavyweights (with actual lawyers they paid) have
>> Randal> already weighed in tha
Thanks.
Apparently the mailing-list is working again.
Stef
On Mar 8, 2010, at 3:13 PM, Lukas Renggli wrote:
> Here are 3 additional tests that verify that these reserved variables
> are not shadowed.
>
> Please integrate :-)
>
> Lukas
>
> On 8 March 2010 15:01, Lukas Renggli wrote:
>> Actual
Note that this email is sent to the Pharo mailing list. It is actually
more appropriate since the moose mailing list members are also part of
Pharo.
I have an update I will push in a day or two that extends namespace
support to attributes and also preserves the order of attributes.
Additi
Naturally in the Pharo Inbox:
Name: Tests-lr.122
Author: lr
Time: 8 March 2010, 3:12:26 pm
UUID: faa9eb31-f84e-4e49-916e-991115a6f2da
Ancestors: Tests-StephaneDucasse.121
- added tests for the compiler to test shadowing of self, super,
thisContext, true, false and nil
On 8 March 2010 15:13, Luka
Erwann just noticed another kind of serious shadowing bug.
The closure compiler allows to declare methods like the following:
foo: self
| super thisContext true false nil |
^ super := thisContext := true := false := nil := self
These argument and temporary names should all be disallowed
> "Randal" == Randal L Schwartz writes:
Randal> And I believe some heavyweights (with actual lawyers they paid) have
Randal> already weighed in that the LGPL is equivalent to the *GPL* in a
Randal> Smalltalk context, so unless the code is explicitly dual-licensed with
Randal> a more permissiv
Hi yanni
I wanted to know if you can tell us what means (unstable) in the report summary
http://hudson.jooshr.org/job/Pharo1.1/81/
is it because the tests cannot run?
Stef
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http:
> "Yanni" == Yanni Chiu writes:
Yanni> GLORP is LGPL, with a subsequently added explanation of how the the
Yanni> license should be interpreted in a Smalltalk context. INAL, but this
Yanni> still seems muddy, since it's unclear whether or not the author's
Yanni> interpretation and intentions
Here are 3 additional tests that verify that these reserved variables
are not shadowed.
Please integrate :-)
Lukas
On 8 March 2010 15:01, Lukas Renggli wrote:
> Actually this is already fixed by the previous fix. Jorge and I are
> going to write some new tests.
>
> Lukas
>
> On 8 March 2010 14:
Actually this is already fixed by the previous fix. Jorge and I are
going to write some new tests.
Lukas
On 8 March 2010 14:50, Lukas Renggli wrote:
> Erwann just noticed another kind of serious shadowing bug.
>
> The closure compiler allows to declare methods like the following:
>
> foo: self
>
28 matches
Mail list logo
