Re: [computer-go] Need for more robust SGF Readers

["Frank de Groot" <frank@xxxxxxxxxxxxx>]

----- Original Message ----- 
From: "Anders Kierulf" <anders@xxxxxxxxxxxxxxxxx>
>
>     It's a text only ... format. Therefore games stored in this format
>     can easily be emailed, posted or processed with text-based tools.
>
> There are ways to encode RTF that will not break existing SGF readers.


I have uploaded another SGF, this time strictly "text only", namely with
Base64.
No escaped characters necessary either.

http://www.zenhacker.com/RTF.sgf

The results:

Parsed within 1 second:

-WinMGT
-cGoban
-gGo
-glGo


100% CPU utilization, after 2 minutes terminated hung program with task
manager:

-SmartGo Reader
-MFOG 11
-MasterGo
-MultiGo


Conclusion: The same programs that had no problems with the "binary" RT
property, also have no problem with the "text" RT property, and the same
programs that had problems with the "binary" RT property have even bigger
problems with the "text" property.

SmartGo was the only program that almost made it neccessary to reset the PC,
it took too many cycles for the PC to stay responsive (super-slow screen
paining etc.) and it took approx. 5 minutes before I could get it to
terminate with the task manager.

Therefore, if to choose between letting a customer's PC lock up when someone
reads my file with the latter 4 programs, or merely read it incorrectly, I
would choose the latter.. It clearly is not a "text vs. binary" issue.
The "binary" solution results in much smaller files as well.

But I think those files may indeed, like Anders mentioned, be postable on
newsgroups so I will do some more testing. In the meantime it would be a
good idea for folks working on SGF parsers to cater for very large property
values.








_______________________________________________
computer-go mailing list
computer-go@xxxxxxxxxxxxxxxxx
http://www.computer-go.org/mailman/listinfo/computer-go/