it a
little bit, and study your proposal, of course.
2014-11-17 9:26 GMT+01:00 Sven Van Caekenberghe s...@stfx.eu:
Hi José,
On 17 Nov 2014, at 02:06, José Comesaña jose.comes...@gmail.com wrote:
There is an annoying error in MultiByteFileStream, reading back when you
have a unicode
There is an annoying error in MultiByteFileStream, reading back when you
have a unicode character. It is also the cause of some FileOut errors. Your
can reproduce it this way:
testString := 'abcdé'.
filename := 'test.txt'.
filename asFileReference ensureDelete.
filename asFileReference
Note that −− is not allowed for parsing reasons (i just checked the
latest version)
now honestly, dont you think that a) is a serious contender? that is all i
wanted to say.
werner
Well, I don't understand why the book says that because in fact you can
define a -- binary method:
comment entries for classes with class side
methods
2014-11-02 17:42 GMT+01:00 Nicolai Hess nicolaih...@web.de:
2014-10-31 0:11 GMT+01:00 José Comesaña jose.comes...@gmail.com:
I see. But WATestError it is in the same package it is Fileing, on
line 3284 and is referenced many times before. I am
I've found this problem in Pharo 3 (seems to happen in Pharo 4 too):
Do:
1. Fileout Seaside-Tests-Core
2. Remove Seaside-Test-Core
3. File in the file created in step 1
You will find:
a. The structure of the package changes.
b. Comments for WaContextTest are lost
c. You get a bunch of errors
2014-10-30 13:16 GMT+01:00 stepharo steph...@free.fr:
On 30/10/14 06:57, José Comesaña wrote:
I've found this problem in Pharo 3 (seems to happen in Pharo 4 too):
Do:
1. Fileout Seaside-Tests-Core
2. Remove Seaside-Test-Core
3. File in the file created in step 1
You will find
I see. But WATestError it is in the same package it is Fileing, on line
3284 and is referenced many times before. I am sorry I have not enough
knowledge about the internals to do more debugging.
Seems to be a lack of coordination between FileOut and FileIn. Maybe
nothing to do...
Now a simpler
-Core-SvenVanCaekenberghe.49
Add support for Fractions and ScaledDecimals as primitive numbers (thx
José Comesaña):
- add Fraction#stonOn: delegating to STONWriter#writeFraction:
- add ScaledDecimal#stonOn: delegating to
STONWriter#writeScaledDecimal:
- extended STONReader#parseNumber to allow
regards
2014-05-31 21:29 GMT+02:00 Sven Van Caekenberghe s...@stfx.eu:
Hi José,
On 31 May 2014, at 01:32, José Comesaña jose.comes...@gmail.com wrote:
Wouldn't it be good if STON could save ScaledDecimals as 12345.678s?.
That way, we could read them back again as ScaledDecimal, instead
in each language
Hope this helps. If someone needs more information, pleas ask.
Best regards
2014-05-31 21:29 GMT+02:00 Sven Van Caekenberghe s...@stfx.eu:
Hi José,
On 31 May 2014, at 01:32, José Comesaña jose.comes...@gmail.com wrote:
Wouldn't it be good if STON could save ScaledDecimals
Oh, sorry, I forgot to write it. And Fraction as well. I have added it for
my own use.
Regards
José
2014-05-31 6:13 GMT+02:00 Joachim Tuchel jtuc...@objektfabrik.de:
Hi,
Sounds good. But I think the Scale should be streamed as well: 12345.678s3
Joachim
José Comesaña jose.comes
If I try to move to another package a class I always get an exception.
Try moving any class present in the standard Pharo 3 to AST-Core, for
example...
Anyway, thanks for the great work you are doing.
Regards
José
Wouldn't it be good if STON could save ScaledDecimals as 12345.678s?. That
way, we could read them back again as ScaledDecimal, instead of Float. I
have tried and it seems quite useful.
Regards
It was already discussed and modified:
https://pharo.fogbugz.com/default.asp?10869
Regards
2013/7/24 Sabine Knöfel sabine.knoe...@gmail.com
Hi,
Date readFrom: '4.2.13' readStream pattern: 'd.m.yy'
Does not return 4.2.2013 but 4.2.0013
The comment is saying
A year given using only two
OK, but I don't know how to make an issue, sorry. :(
2013/6/14 Sven Van Caekenberghe s...@stfx.eu
On 14 Jun 2013, at 11:44, José Comesaña jose.comes...@gmail.com wrote:
I think I've found a bug in String classreadFrom:. This sentence fails:
z := String readFrom: 'Good morning
Fix and test sent.
Regards.
2013/6/14 Sven Van Caekenberghe s...@stfx.eu
No problem, here is the issue
https://pharo.fogbugz.com/f/cases/10915/String-class-readFrom-is-broken-and-untested
I will produce a slice later on.
On 14 Jun 2013, at 11:58, José Comesaña jose.comes...@gmail.com
Done.
Sorry for my ignorance, :).
Thanks
2013/6/7 Stéphane Ducasse stephane.duca...@inria.fr
thanks :)
This is less work for us and the process can automatically check the code
and run the tests automatically.
Stef
Answers in red.
Regards
2013/6/7 Sven Van Caekenberghe s...@stfx.eu
On 07 Jun 2013, at 13:26, José Comesaña jose.comes...@gmail.com wrote:
Thank you Sven.
I had made the fixes myself, creating a new class for dates (I don't
need the complexity of Date just for determining if a date
Hi again.
I have one first test for #readFrom:pattern:. What can I do now to send it,
where, to whom?.
Regards
2013/6/7 Sven Van Caekenberghe s...@stfx.eu
On 07 Jun 2013, at 14:28, José Comesaña jose.comes...@gmail.com wrote:
Answers in red.
Regards
2013/6/7 Sven Van Caekenberghe
:28, José Comesaña jose.comes...@gmail.com wrote:
Answers in red.
Regards
2013/6/7 Sven Van Caekenberghe s...@stfx.eu
On 07 Jun 2013, at 13:26, José Comesaña jose.comes...@gmail.com
wrote:
Thank you Sven.
I had made the fixes myself, creating a new class for dates (I don't
20 matches
Mail list logo
