And now it is published as well: === Name: ConfigurationOfZincHTTPComponents-SvenVanCaekenberghe.66 Author: SvenVanCaekenberghe Time: 10 June 2014, 10:22:30.144809 pm UUID: 7a18f667-bff7-4989-ab5f-bfefca108754 Ancestors: ConfigurationOfZincHTTPComponents-SvenVanCaekenberghe.65 fix a syntax and portability issue in the #catalogKeywords list (thx Paul DeBruicker) === On 10 Jun 2014, at 22:17, Paul DeBruicker <pdebruic@gmail.com> wrote:
Hi Sven,
Your proposed version works just fine. Thanks for making the change, and thanks Jenkin/TravisCI....
Paul
Sven Van Caekenberghe-2 wrote
Hi Paul,
It is good that you picked this up so quickly, since I just committed it a couple of hours ago.
Would
#catalogKeywords ^ #(#networking #internet #http #client #server #request #response #url #'mime-type' #'character-encoding')
be good as well (I don't know what the limitations are in Gemstone) ?
I added the hyphen on purpose, because I think that is more correct and better when some future tools might search through the keywords.
Sven
On 10 Jun 2014, at 21:57, Paul DeBruicker <
pdebruic@
> wrote:
The current method is
#catalogKeywords ^ #(#networking #internet #http #client #server #request #response #url #mime-type #character-encoding)
Can we change it to
#catalogKeywords ^ #(#networking #internet #http #client #server #request #response #url #mimeType #characterEncoding)
So the GemStone parser can handle it?
Thanks
Paul
-- View this message in context: http://forum.world.st/ConfigurationOfZincHTTPComponents-class-catalogKeyword... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.