[Pharo-project] Next step in cleaning DataStream
So, so far we have removed SmartRefStream, deprecated ReferenceStream and integrated Fuel. The ONLY remaining user for DataStream is Monticello. We do not want to replace that yet because Fuel may still change the format and we do not want to break monticello versions. But, my question is now...should we clean DataStream and assume its only usage will be the definitions of Monticello? becuase I true, I think we may be able to remove DiskProxy and all its users, togethet with lots of methods like #objectForDataStream: what do you think? -- Mariano http://marianopeck.wordpress.com
4. 6. 2012 v 17:58, Mariano Martinez Peck <marianopeck@gmail.com>:
So, so far we have removed SmartRefStream, deprecated ReferenceStream and integrated Fuel. The ONLY remaining user for DataStream is Monticello. We do not want to replace that yet because Fuel may still change the format and we do not want to break monticello versions. But, my question is now...should we clean DataStream and assume its only usage will be the definitions of Monticello? becuase I true, I think we may be able to remove DiskProxy and all its users, togethet with lots of methods like #objectForDataStream:
what do you think?
I think it is a good proposal. Then it can be in separate package or as part of MC package. -- Pavel
-- Mariano http://marianopeck.wordpress.com
On Mon, Jun 4, 2012 at 6:09 PM, Pavel Krivanek <pavel.krivanek@gmail.com> wrote:
I think it is a good proposal. Then it can be in separate package or as part of MC package.
I would put DataStream and its friends within the monticello package, and prepend MC to their names. Then, you can clean the resulting classes if you want to. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry
On Jun 4, 2012, at 6:16 PM, Damien Cassou wrote:
On Mon, Jun 4, 2012 at 6:09 PM, Pavel Krivanek <pavel.krivanek@gmail.com> wrote:
I think it is a good proposal. Then it can be in separate package or as part of MC package.
I would put DataStream and its friends within the monticello package, and prepend MC to their names. Then, you can clean the resulting classes if you want to.
Yes, I think that is what we should do. Marcus -- Marcus Denker -- http://marcusdenker.de
good idea. And for fuel we should really see how to support migration between formats. Or not change it :) Stef On Jun 5, 2012, at 8:50 AM, Marcus Denker wrote:
On Jun 4, 2012, at 6:16 PM, Damien Cassou wrote:
On Mon, Jun 4, 2012 at 6:09 PM, Pavel Krivanek <pavel.krivanek@gmail.com> wrote:
I think it is a good proposal. Then it can be in separate package or as part of MC package.
I would put DataStream and its friends within the monticello package, and prepend MC to their names. Then, you can clean the resulting classes if you want to.
Yes, I think that is what we should do.
Marcus
-- Marcus Denker -- http://marcusdenker.de
+1 On Jun 4, 2012, at 6:15 PM, Damien Cassou wrote:
On Mon, Jun 4, 2012 at 6:09 PM, Pavel Krivanek <pavel.krivanek@gmail.com> wrote:
I think it is a good proposal. Then it can be in separate package or as part of MC package.
I would put DataStream and its friends within the monticello package, and prepend MC to their names. Then, you can clean the resulting classes if you want to.
-- Damien Cassou http://damiencassou.seasidehosting.st
"Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry
Ok. Perfect. So let's assume DataStream is used only for Motnicello. I will rename it to MCDataStream, move it to Monticello Package and see all what I can remove/clean. I will let you know. Cheers On Tue, Jun 5, 2012 at 12:51 PM, Esteban Lorenzano <estebanlm@gmail.com>wrote:
+1
On Jun 4, 2012, at 6:15 PM, Damien Cassou wrote:
On Mon, Jun 4, 2012 at 6:09 PM, Pavel Krivanek <pavel.krivanek@gmail.com> wrote:
I think it is a good proposal. Then it can be in separate package or as part of MC package.
I would put DataStream and its friends within the monticello package, and prepend MC to their names. Then, you can clean the resulting classes if you want to.
-- Damien Cassou http://damiencassou.seasidehosting.st
"Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry
-- Mariano http://marianopeck.wordpress.com
Guys..the fact of having to make everything deprecated instead of removing it is really a pain. Now ReferenceStream is not removed but deprecated..meaning that it *should* work. So instead of removing everything I have to change it a lot so that it "still" works but deprecated. Can we just assume that ReferenceStream will be removed in 2.0 please? On Tue, Jun 5, 2012 at 1:32 PM, Mariano Martinez Peck <marianopeck@gmail.com
wrote:
Ok. Perfect. So let's assume DataStream is used only for Motnicello. I will rename it to MCDataStream, move it to Monticello Package and see all what I can remove/clean. I will let you know.
Cheers
On Tue, Jun 5, 2012 at 12:51 PM, Esteban Lorenzano <estebanlm@gmail.com>wrote:
+1
On Jun 4, 2012, at 6:15 PM, Damien Cassou wrote:
On Mon, Jun 4, 2012 at 6:09 PM, Pavel Krivanek < pavel.krivanek@gmail.com> wrote:
I think it is a good proposal. Then it can be in separate package or as part of MC package.
I would put DataStream and its friends within the monticello package, and prepend MC to their names. Then, you can clean the resulting classes if you want to.
-- Damien Cassou http://damiencassou.seasidehosting.st
"Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry
-- Mariano http://marianopeck.wordpress.com
-- Mariano http://marianopeck.wordpress.com
On Tue, Jun 5, 2012 at 3:36 PM, Mariano Martinez Peck <marianopeck@gmail.com
wrote:
Guys..the fact of having to make everything deprecated instead of removing it is really a pain. Now ReferenceStream is not removed but deprecated..meaning that it *should* work. So instead of removing everything I have to change it a lot so that it "still" works but deprecated. Can we just assume that ReferenceStream will be removed in 2.0 please?
And moreover, I have another question. With this change, I remove DiskProxy and if I move MCDataStream to Monticello package, then the only class that remains in System-Object Storage is DeepCopier. It makes no sense to keep only that class there. So, I vote for removing the package and move that class somewhere. Now.. any ideas what that "somewhere" could be?
On Tue, Jun 5, 2012 at 1:32 PM, Mariano Martinez Peck < marianopeck@gmail.com> wrote:
Ok. Perfect. So let's assume DataStream is used only for Motnicello. I will rename it to MCDataStream, move it to Monticello Package and see all what I can remove/clean. I will let you know.
Cheers
On Tue, Jun 5, 2012 at 12:51 PM, Esteban Lorenzano <estebanlm@gmail.com>wrote:
+1
On Jun 4, 2012, at 6:15 PM, Damien Cassou wrote:
On Mon, Jun 4, 2012 at 6:09 PM, Pavel Krivanek < pavel.krivanek@gmail.com> wrote:
I think it is a good proposal. Then it can be in separate package or as part of MC package.
I would put DataStream and its friends within the monticello package, and prepend MC to their names. Then, you can clean the resulting classes if you want to.
-- Damien Cassou http://damiencassou.seasidehosting.st
"Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry
-- Mariano http://marianopeck.wordpress.com
-- Mariano http://marianopeck.wordpress.com
-- Mariano http://marianopeck.wordpress.com
On Tue, Jun 5, 2012 at 3:36 PM, Mariano Martinez Peck <marianopeck@gmail.com
wrote:
Guys..the fact of having to make everything deprecated instead of removing it is really a pain. Now ReferenceStream is not removed but deprecated..meaning that it *should* work. So instead of removing everything I have to change it a lot so that it "still" works but deprecated. Can we just assume that ReferenceStream will be removed in 2.0 please?
In addition, if someone is really worried about ReferenceStream then he can always do a fileout of 1.4 and import it in Pharo 2.0 (and adapt it if necessary)
On Tue, Jun 5, 2012 at 1:32 PM, Mariano Martinez Peck < marianopeck@gmail.com> wrote:
Ok. Perfect. So let's assume DataStream is used only for Motnicello. I will rename it to MCDataStream, move it to Monticello Package and see all what I can remove/clean. I will let you know.
Cheers
On Tue, Jun 5, 2012 at 12:51 PM, Esteban Lorenzano <estebanlm@gmail.com>wrote:
+1
On Jun 4, 2012, at 6:15 PM, Damien Cassou wrote:
On Mon, Jun 4, 2012 at 6:09 PM, Pavel Krivanek < pavel.krivanek@gmail.com> wrote:
I think it is a good proposal. Then it can be in separate package or as part of MC package.
I would put DataStream and its friends within the monticello package, and prepend MC to their names. Then, you can clean the resulting classes if you want to.
-- Damien Cassou http://damiencassou.seasidehosting.st
"Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry
-- Mariano http://marianopeck.wordpress.com
-- Mariano http://marianopeck.wordpress.com
-- Mariano http://marianopeck.wordpress.com
participants (6)
-
Damien Cassou -
Esteban Lorenzano -
Marcus Denker -
Mariano Martinez Peck -
Pavel Krivanek -
Stéphane Ducasse