[Pharo-project] Where does Regex-Core and friends live
I am porting the latest Regex to GemStone and in the interest of Pharo compatibility, I found Regex-Core and and Regex-Tests-Core in the Pharo repository. In loading Regex-Tests-Core I found some compile errors (doubled '.', a common porting problem) in RxParserTest>>testTranslatingMatchesUsing and RxParserTest>>test, but I don't know where the home repository (other then Pharo) resides, where I could submit my updates. I've got a GemSource repository, but I'm actually hoping (haven't run tests yet:) that I will be able to use Regex-Core without making any GemStone-specific changes ... Dale
hi Dale! I do not know about your need. But personally, if I have to deal with non trivial parsing, I will use PetitParser. Lukas made a tutorial last week and I am convinced. Cheers, Alexandre On 8 Dec 2010, at 20:57, Dale Henrichs wrote:
I am porting the latest Regex to GemStone and in the interest of Pharo compatibility, I found Regex-Core and and Regex-Tests-Core in the Pharo repository.
In loading Regex-Tests-Core I found some compile errors (doubled '.', a common porting problem) in RxParserTest>>testTranslatingMatchesUsing and RxParserTest>>test, but I don't know where the home repository (other then Pharo) resides, where I could submit my updates.
I've got a GemSource repository, but I'm actually hoping (haven't run tests yet:) that I will be able to use Regex-Core without making any GemStone-specific changes ...
Dale
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On 12/08/2010 06:21 PM, Alexandre Bergel wrote:
hi Dale!
I do not know about your need. But personally, if I have to deal with non trivial parsing, I will use PetitParser. Lukas made a tutorial last week and I am convinced.
Cheers, Alexandre
On 8 Dec 2010, at 20:57, Dale Henrichs wrote:
I am porting the latest Regex to GemStone and in the interest of Pharo compatibility, I found Regex-Core and and Regex-Tests-Core in the Pharo repository.
In loading Regex-Tests-Core I found some compile errors (doubled '.', a common porting problem) in RxParserTest>>testTranslatingMatchesUsing and RxParserTest>>test, but I don't know where the home repository (other then Pharo) resides, where I could submit my updates.
I've got a GemSource repository, but I'm actually hoping (haven't run tests yet:) that I will be able to use Regex-Core without making any GemStone-specific changes ...
Dale
I'm interested in terms of maintaining Pharo compatibility ... many of the GLASS developers develop in Pharo and deploy in GemStone and I am trying to get in the habit of using the same packages that are loaded into Pharo (where possible/practical) so that the bugfixes and updates can be shared without too much trouble ... Dale
Ok, it makes sense Alexandre On 9 Dec 2010, at 13:47, Dale Henrichs wrote:
On 12/08/2010 06:21 PM, Alexandre Bergel wrote:
hi Dale!
I do not know about your need. But personally, if I have to deal with non trivial parsing, I will use PetitParser. Lukas made a tutorial last week and I am convinced.
Cheers, Alexandre
On 8 Dec 2010, at 20:57, Dale Henrichs wrote:
I am porting the latest Regex to GemStone and in the interest of Pharo compatibility, I found Regex-Core and and Regex-Tests-Core in the Pharo repository.
In loading Regex-Tests-Core I found some compile errors (doubled '.', a common porting problem) in RxParserTest>>testTranslatingMatchesUsing and RxParserTest>>test, but I don't know where the home repository (other then Pharo) resides, where I could submit my updates.
I've got a GemSource repository, but I'm actually hoping (haven't run tests yet:) that I will be able to use Regex-Core without making any GemStone-specific changes ...
Dale
I'm interested in terms of maintaining Pharo compatibility ... many of the GLASS developers develop in Pharo and deploy in GemStone and I am trying to get in the habit of using the same packages that are loaded into Pharo (where possible/practical) so that the bugfixes and updates can be shared without too much trouble ...
Dale
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
I'm interested in terms of maintaining Pharo compatibility ... many of the GLASS developers develop in Pharo and deploy in GemStone and I am trying to get in the habit of using the same packages that are loaded into Pharo (where possible/practical) so that the bugfixes and updates can be shared without too much trouble ...
Dale we are interested in making sure that the package loads well in Glass. I hope that we will simplify clean the system another couple of times to arrive to a nicer version. Adding tests is also a good way to support such effort. Stef
On 12/09/2010 10:39 AM, Stéphane Ducasse wrote:
I'm interested in terms of maintaining Pharo compatibility ... many of the GLASS developers develop in Pharo and deploy in GemStone and I am trying to get in the habit of using the same packages that are loaded into Pharo (where possible/practical) so that the bugfixes and updates can be shared without too much trouble ...
Dale
we are interested in making sure that the package loads well in Glass. I hope that we will simplify clean the system another couple of times to arrive to a nicer version. Adding tests is also a good way to support such effort.
Stef
Stef, The packages loaded (except for the two compile errors .. I'll check a fix in for those) and all tests ran clean ... I will probably spend some time with regex and streams to validate GemStone's Ansi streams and will add tests if the coverage is lacking in that area ... Dale
cool! On Dec 9, 2010, at 10:41 PM, Dale Henrichs wrote:
On 12/09/2010 10:39 AM, Stéphane Ducasse wrote:
I'm interested in terms of maintaining Pharo compatibility ... many of the GLASS developers develop in Pharo and deploy in GemStone and I am trying to get in the habit of using the same packages that are loaded into Pharo (where possible/practical) so that the bugfixes and updates can be shared without too much trouble ...
Dale
we are interested in making sure that the package loads well in Glass. I hope that we will simplify clean the system another couple of times to arrive to a nicer version. Adding tests is also a good way to support such effort.
Stef
Stef,
The packages loaded (except for the two compile errors .. I'll check a fix in for those) and all tests ran clean ... I will probably spend some time with regex and streams to validate GemStone's Ansi streams and will add tests if the coverage is lacking in that area ...
Dale
I've looked over the tests and it looks like all of the match operations ultimately end up running against a stream, so the fact that the tests pass on GemStone indicates that the stream behavior is pretty well covered ... so no obvious holes in the test suite.. Dale On 12/09/2010 01:41 PM, Dale Henrichs wrote:
On 12/09/2010 10:39 AM, Stéphane Ducasse wrote:
I'm interested in terms of maintaining Pharo compatibility ... many of the GLASS developers develop in Pharo and deploy in GemStone and I am trying to get in the habit of using the same packages that are loaded into Pharo (where possible/practical) so that the bugfixes and updates can be shared without too much trouble ...
Dale
we are interested in making sure that the package loads well in Glass. I hope that we will simplify clean the system another couple of times to arrive to a nicer version. Adding tests is also a good way to support such effort.
Stef
Stef,
The packages loaded (except for the two compile errors .. I'll check a fix in for those) and all tests ran clean ... I will probably spend some time with regex and streams to validate GemStone's Ansi streams and will add tests if the coverage is lacking in that area ...
Dale
On Dec 9, 2010, at 12:57 AM, Dale Henrichs wrote:
I am porting the latest Regex to GemStone and in the interest of Pharo compatibility, I found Regex-Core and and Regex-Tests-Core in the Pharo repository.
In loading Regex-Tests-Core I found some compile errors (doubled '.', a common porting problem) in RxParserTest>>testTranslatingMatchesUsing and RxParserTest>>test, but I don't know where the home repository (other then Pharo) resides, where I could submit my updates.
commit in the inbox
I've got a GemSource repository, but I'm actually hoping (haven't run tests yet:) that I will be able to use Regex-Core without making any GemStone-specific changes ...
Yes I hope too
Dale
I am porting the latest Regex to GemStone and in the interest of Pharo compatibility, I found Regex-Core and and Regex-Tests-Core in the Pharo repository.
The latest code is in <http://source.lukas-renggli.ch/unsorted/>. It is a full port of the latest code from VisualWorks + various critical bug fixes. Except for the packaging (which is identical to VisualWorks), it should be the same as the code in Pharo. Lukas -- Lukas Renggli www.lukas-renggli.ch
On 12/08/2010 11:44 PM, Lukas Renggli wrote:
I am porting the latest Regex to GemStone and in the interest of Pharo compatibility, I found Regex-Core and and Regex-Tests-Core in the Pharo repository.
The latest code is in<http://source.lukas-renggli.ch/unsorted/>.
It is a full port of the latest code from VisualWorks + various critical bug fixes.
Except for the packaging (which is identical to VisualWorks), it should be the same as the code in Pharo.
Lukas
My first choice is to use the packages that are loaded into Pharo, since I am trying to maintain Pharo compatibility, so I want the packaging changes as well ... Dale
I've got a GemSource repository, but I'm actually hoping (haven't run tests yet:) that I will be able to use Regex-Core without making any GemStone-specific changes ...
That's unlikely, because the code makes quite some absolute stream positioning like aStream position = 0, aStream position = aStream size, etc. Lukas -- Lukas Renggli www.lukas-renggli.ch
On 12/08/2010 11:50 PM, Lukas Renggli wrote:
I've got a GemSource repository, but I'm actually hoping (haven't run tests yet:) that I will be able to use Regex-Core without making any GemStone-specific changes ...
That's unlikely, because the code makes quite some absolute stream positioning like aStream position = 0, aStream position = aStream size, etc.
Lukas
Lukas, I've pulled down the Ansi compatible stream implementations (where position has been fixed) that I was using for Grease and all of the tests pass, so unless there are some corner cases I'm missing (always a possibility) GemStone-specific changes aren't needed... Dale
participants (4)
-
Alexandre Bergel -
Dale Henrichs -
Lukas Renggli -
Stéphane Ducasse