by calling tail -5 through OSProcess
> on Linux for a quick fix.
>
> tac file can also help to read a file in reverse.
>
> Phil
>
> On Mon, Nov 17, 2014 at 10:20 AM, José Comesaña
> wrote:
>
>> Thank you Sven.
>>
>> I an trying to read a vry long
little bit, and study your proposal, of course.
2014-11-17 9:26 GMT+01:00 Sven Van Caekenberghe :
> Hi José,
>
> > On 17 Nov 2014, at 02:06, José Comesaña wrote:
> >
> > There is an annoying error in MultiByteFileStream, reading back when you
> have a unicode char
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
writeStream
>
> "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:
Sm
https://pharo.fogbugz.com/default.asp?14377>
>>> FileOut creates invalid comment entries for classes with class side
>>> methods
>>>
>>>
>>> 2014-11-02 17:42 GMT+01:00 Nicolai Hess :
>>>
>>>> 2014-10-31 0:11 GMT+01:00 José Come
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
2014-10-30 13:16 GMT+01:00 stepharo :
>
> 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
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 in
4c992-4f32-4f3a-8853-a4a9cf55c453
> Ancestors: STON-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>&
5918715072783319 and denominator 4398046511104 and the second
has numerator 33644 and denominator 25. I still have to fix this.
Hope not to bore you too much.
Regards
2014-06-02 1:56 GMT+02:00 José Comesaña :
> And this is an improved version. More changes to avoid parsing weird
> thing
k isDigit ]
>
> why not create a temporary string (including possibility of $e, $s, $/,
> even $@ ...) to that point (tmpString) and do:
>
> number := Number readFromString: tmpString
>
> That way, we would have a "native" parsing in each language
>
> Hope th
someone needs more information, pleas ask.
Best regards
2014-05-31 21:29 GMT+02:00 Sven Van Caekenberghe :
> Hi José,
>
> On 31 May 2014, at 01:32, José Comesaña wrote:
>
> > Wouldn't it be good if STON could save ScaledDecimals as 12345.678s?.
> That way, we could read
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é
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 :
> Hi,
>
> Sounds good. But I think the Scale should be streamed as well: 12345.678s3
>
> Joachim
>
> José Comesaña schrieb:
>
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
t 2:34 PM, José Comesaña
> wrote:
>
> > It was already discussed and modified:
> https://pharo.fogbugz.com/default.asp?10869
> >
>
> This one is just an open report… no action was done. I have merged it into
> Issue 11222
>
> But there is a third issue about ex
It was already discussed and modified:
https://pharo.fogbugz.com/default.asp?10869
Regards
2013/7/24 Sabine Knöfel
> 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 decimals is consid
Fix and test sent.
Regards.
2013/6/14 Sven Van Caekenberghe
> 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 wrot
OK, but I don't know how to make an issue, sorry. :(
2013/6/14 Sven Van Caekenberghe
>
> On 14 Jun 2013, at 11:44, José Comesaña wrote:
>
> > I think I've found a bug in String class>>readFrom:. This sentence fails:
> >
> > z := String readFrom:
I think I've found a bug in String class>>readFrom:. This sentence fails:
z := String readFrom: 'Good morning' readStream.
I think that the bug is on the first line, saying: ^ self class
streamContents:. The 'class' message shouldn't be here, because 'self'
itself refers to the String class.
Pre
Done.
Sorry for my ignorance, :).
Thanks
2013/6/7 Stéphane Ducasse
> thanks :)
> This is less work for us and the process can automatically check the code
> and run the tests automatically.
> Stef
>
>
gt; On Jun 7, 2013, at 9:12 PM, Stéphane Ducasse
> wrote:
>
>> tx I will look at it.
>>
>> Stef
>>
>> On Jun 7, 2013, at 8:57 PM, José Comesaña wrote:
>>
>>> Done.
>>>
>>> I hope I have made it correctly. If
; I have one first test for #readFrom:pattern:. What can I do now to send
> it, where, to whom?.
>
>
> I will create a bug entry for you and you create a slice with the test and
> the fix and you publish it in the pharo inbox.
>
> Stef
>
>
> Regards
>
> 2013/
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
>
> On 07 Jun 2013, at 14:28, José Comesaña wrote:
>
> > Answers in red.
> >
> > Regards
> >
> > 2013/6/7 S
Answers in red.
Regards
2013/6/7 Sven Van Caekenberghe
>
> On 07 Jun 2013, at 13:26, José Comesaña 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 determinin
yway, your solution does not work for the 'd/m/y' pattern, although it
does for 'd/m/yy'.
I could write the tests you suggest, if you think they are interesting.
Regards
2013/6/7 Sven Van Caekenberghe
> Hi José,
>
> On 07 Jun 2013, at 12:02, José Comesaña wrote:
>
&g
Hello everybody.
I would like to add a new improvement to this thread.
I have noticed that Date class has a bug, or at least something to improve
in readFrom:pattern: method. The initial comment states that "A year given
using only two decimals is considered to be >2000.".
But this seems to be i
27 matches
Mail list logo
