2017-01-22 11:54 GMT+01:00 Guillermo Polito <guillermopol...@gmail.com>:
> Stef, we need to think about it carefullly. Streams are used in the kernel
> for many tasks. Replacing them by a big framework will be a huge drawback
> for bootstrapping purposes.
>
I would not say that Xtreams is bigger library then current streams in
system. I measure it a bit:
"5 packages: core parts + file streams + socket streams"
ps := RPackageOrganizer default packages select: [ :each | each name
beginsWith: 'Xtreams-' ].
ps sum: [ :each | each definedClasses size ] "45".
ps sum: [ :each | (each definedClasses sum: [ :c | c methods size ])
+ each extensionMethods size] "585".
And current streams:
Stream package definedClasses size "13".
(Stream package definedClasses sum: [ :c | c methods size ])
+ Stream package extensionMethods size "304".
({AbstractBinaryFileStream. FileStream} flatCollect: #withAllSubclasses)
size."6"
({AbstractBinaryFileStream. FileStream} flatCollect: #withAllSubclasses)
sum: [ :c | c methods size ]."226"
SocketStream methods size "81"
So in summary current streams are ~600 methods which is similar to xtreams.
But maybe current streams is much bigger code base. I not take into account
compression part, encodings and others.
Anyway idea to replace current streams completely is huge task. I doubt
that we can move such way.
