> > > Tests indicate that, in ooRexx5 in Windows, code like > linein(f), lines(f), charin(f), chars(f) > causes a huge slowdown vis-a-vis their ooRexx counterparts > s~linein, s~lines, s~charin, s~chars > > A likely cause is indicated in Rick McGuire's comment in email thread > shown under bug1721 (bug1737 also has this issue at its core) > ///// > If you are using the stream objects directly, there is no need to resolve > the file name information on each write. > If you are using the builtin functions, then it needs to resolve it to > retrieve the correct stream object from the table of open objects that the > context is managing. > \\\\\ > > Any clues when this problem could have been introduced in v5? > > There is another Windows issue re case-sensitive filenames > (bug1656). Erich has pinpointed when that problem was > introduced > > > Tests indicate that, in ooRexx5 in Windows, code like > linein(f), lines(f), charin(f), chars(f) > causes a huge slowdown vis-a-vis their ooRexx counterparts > s~linein, s~lines, s~charin, s~chars > > A likely cause is indicated in Rick McGuire's comment in email thread > shown under bug1721 (bug1737 also has this issue at its core) > ///// > If you are using the stream objects directly, there is no need to resolve > the file name information on each write. > If you are using the builtin functions, then it needs to resolve it to > retrieve the correct stream object from the table of open objects that the > context is managing. > \\\\\ > > Any clues when this problem could have been introduced in v5? > > There is another Windows issue re case-sensitive filenames > (bug1656). Erich has pinpointed when that problem was > introduced > > The slowdown problem may be tested using Rony's testdata.txt > created by createTextFile.rex under #1737 documents. I used > a simple test suite based on that. > > > >
_______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
