f you take some notes let me know :)
> And I appreciate the work you've done on Pharo and Squeak over the years. I
> learned Smalltalk through Pharo By Example, and there are probably many
> others who also did.
>
>>
>> - Original Message -
>> From: Sté
> In any case, it is strange that the items in the CharacterSet cannot be
> printed by the EyeInspector. GTInspector shows them properly (see attached).
>
> It gets even worse. Try doing this in a fresh Pharo 3.0 image:
>
>CharacterSet allCharacters explore
probably because the explor
I read a bit about internal public and other dtd and it looks like this is ok
Ahhh.
The bug was showing a parser problem…. so I could not get that it was related
to the network :)
> Because monty's code downloads the DTD for validation from
>
> http://www.musicxml.org/dtds/partwise.dtd
>
> I
Because monty's code downloads the DTD for validation from
http://www.musicxml.org/dtds/partwise.dtd
I should check if is the "right thing to do" because it would increase
parsing time significantly. At least it should be an option.
Cheers,
Hernan
2013/12/27 Stéphane Ducasse
> XMLDOMParser
I do not know but monty adding worth behavior.
Now we could always revert to the previous configuration version.
Stef
Here is the mail that he sent a while ago:
These updates add validation against internal and external DTDs, proper
replacement of general and parameter entites, customizable re
In an image with XML-Parser-NorbertHartl.141 both expression work.
I see that in PharoExtras/XMLParser there are many commits by ‘monty’ all with
empty log messages - how is that possible ??
On 27 Dec 2013, at 16:57, Stéphane Ducasse wrote:
> XMLDOMParser parse: '
> "-//Recordare//DTD MusicX
XMLDOMParser parse: '
http://www.musicxml.org/dtds/partwise.dtd";>
Music
' readStream.
produces the error
while
XMLDOMParser parse: '
Music
' readStream.
does not.
Stef
It seems logical that a CharacterSet contains Characters even if its internal
implementation uses a bitmap, its API should - I would expect.
If nextChar is an Integer in the first code piece, maybe you are reading from a
binary stream instead of from a character stream ?
On 27 Dec 2013, at 16:3
Hi
I’m trying to understand asciiValue
skipSeparators
| nextChar |
[(nextChar := self peek) not Nil
and: [SeparatorCharacters includes: nextChar]]
whileTrue: [self next].
SeparatorCharacters is a CharacterSet
nextChar is an integer
and
Charac
I pushed the latest version of the configuration to the MetacelloRepository.
Now unfortunately the last version still has the same problem.
stef
On 23 Dec 2013, at 18:26, NISHIHARA Satoshi wrote:
> Hello
>
> using: Pharo3.0 Latest update: #30659 (it occurs same error to
> Pharo2.0 Latest updat
ok I missed the example in the mail of satoshi I will try to have a look or at
leat write a test.
On 25 Dec 2013, at 19:04, Stéphane Ducasse wrote:
> Hi Hernan
>
> how did you reproduce the bug?
> Because it would be nice to fix it.
>
> Stef
>
> On 24 Dec 2013, at 18:48, Hernán Morales Duran
I am not sure because XML changed a lot, but this method
entityURIFromRelative: aRelativeUri andBase: aBaseUri
^ ((self httpClient beginsWithSupportedURLProtocol: aRelativeUri)
ifTrue: [self httpClient]
ifFalse: [self fileClient])
combineRelative: aRelativeUri
Hi Hernan
how did you reproduce the bug?
Because it would be nice to fix it.
Stef
On 24 Dec 2013, at 18:48, Hernán Morales Durand
wrote:
> I have tried in Pharo 2.0 configurations from Config Browser
> (ConfigurationOfXMLParser-StephaneDucasse.16) and latest from
> http://www.smalltalkhub.c
I have tried in Pharo 2.0 configurations from Config Browser
(ConfigurationOfXMLParser-StephaneDucasse.16) and latest from
http://www.smalltalkhub.com/mc/PharoExtras/XMLParser/main(ConfigurationOfXMLParser-monty.37)
and both have this bug.
Hernán
2013/12/24 Stéphane Ducasse
> Hi Satoshi
>
> Di
Hi Satoshi
Did you try with the latest configuration of XMLParser?
Because I do not know what it is in Moose.
Stef
On 23 Dec 2013, at 18:26, NISHIHARA Satoshi wrote:
> Hello
>
> using: Pharo3.0 Latest update: #30659 (it occurs same error to
> Pharo2.0 Latest update: #20628)
> (Moose 4.9 with X
Hello
using: Pharo3.0 Latest update: #30659 (it occurs same error to
Pharo2.0 Latest update: #20628)
(Moose 4.9 with XML-Parser (DamienCassou.143) has no_err)
1. load XMLParser (StephaneDucasse.16) from Configuration browser
2. select and inspect it below:
^ XMLDOMParser parse: '
http://www.musi
16 matches
Mail list logo
