- Pharo-users - lists.pharo.org

Re: [Pharo-users] [squeak-dev] Now available: a database conectivity API and its MySQL implementation

by Mariano Martinez Peck

On Thu, Sep 29, 2011 at 5:04 PM, Anindya Haldar <anindya_haldar(a)yahoo.com>wrote: > Hi Mariano, > > A couple of things with some history can perhaps explain this a bit better. > > - This all started almost a couple of years ago, when I was looking for a > JDBC/DBI style API with MySQL support. > - There was a MySQL driver, although a bit dated, and it lacked certain > features I thought would be pretty compelling to have. > - At that time I was not aware of OpenDBX, and even today I know very > little about it. That is not a reflection on OpenDBX, it is my own > limitation > - I always wished for a rich, consistent database API with native Smalltalk > drivers in Squeak/Pharo. > - Since the protocol driver talks MySQL packets, and it should be possible > to implement the DBXTalk API on top of it, in the same way the StdbMysqlImpl > implements StdbCore API on top of the protocol driver. You may have noticed > that the protocol driver is a separate project, and should be usable by any > other projects for implementing another type/style of driver API > > I fully recognize your point here. I do wish all success to the DBX > project. > > In my case it was just some long-drawn ans slow personal effort that I > thought the result might be useful to the community. > > Hi Anindya. Please, do not misunderstood me. I am really happy that there is more effort in the relational world, and your work is amazing. It is TOTALLY useful for the community. I wish we could have even more native drivers and use less FFI. That's awesome. So, please go on with your work. Previously, Glorp port to squeak has totally hardcoded to the PostgreSQL driver. Now, we have totally separated that, and we have a DatabaseDriver abstract class. It should be easy for you to create a subclass and create a concrete GlorpMySQLNativeDriver :) So you can have Glorp working out of the box. Another alternative is to adapt your driver (subclass in our DBXTAlk model) that delegates to your driver. That way you can use OpenDBX API with your driver, which means that you can also use Glorp for example. If you are interested, please let me know and I can go further in the details :) Best regards, > Best, > Anindya > > ------------------------------ > *From:* Mariano Martinez Peck <marianopeck(a)gmail.com> > *To:* Anindya Haldar <anindya_haldar(a)yahoo.com>; " > pharo-users(a)lists.gforge.inria.fr" <pharo-users(a)lists.gforge.inria.fr> > *Sent:* Thursday, September 29, 2011 1:25 AM > *Subject:* Re: [squeak-dev] Now available: a database conectivity API and > its MySQL implementation > > Hi Anindya. Nice to hear more effort on this front. > > Is there any particular reason of spending all this amount of work consider > we already have DBXTalk? wouldn't be better to improve the former? > DBXTalk is exactly the same, and it is already working with Oracle, MySQL, > PostgreSQL, SQL Server, Sqlite3, Sybase, etc. The main problem is that we > depend on an external library like OpenDBX. I guess you are using a native > connection with sockets. > Moreover, we have ported Glorp and adapt it to use DBXTalk driver. > > What I mean is that we can join forces. For example, if you did an > implementation of the MySQL natively (if fact, there is already one in > squeaksource although it is a little bit outdated), we could try to make the > same API as DBXTalk. That way, still with the same API we can use your > driver. And you can use Glorp with your driver as well. > > Cheers > > > On Thu, Sep 29, 2011 at 10:11 AM, Anindya Haldar <anindya_haldar(a)yahoo.com > > wrote: > > I am extremely pleased to offer to the community a generic Smalltalk API > for database connectivity API, along with a MySQL implementation written > from ground up. Think of JDBC and DBI like interfaces in other languages and > environments, and this one offers abstract facilities like connection, > prepared statement, resultset, row, metdata and so on for the application. > > The API implementation uses driver delegates, and insulates the > applications from the driver specific interfaces. As of now, a MySQL > implementation is available, with other databases engine supports in the > future plans. > > The API supports server side prepared statements and cursor based fetch > implemented in the MySQL driver. > > The implementation is currently available in 3 parts: > > 1) StdbCore project: This is primarily the API definitions and the > delegation logic > URL: http://www.squeaksource.com/StdbCore.html > > 2) StdbMysqlImpl project: This is the MySQL implementation of the StdbCore > API > URL: http://www.squeaksource.com/StdbMysqlImpl.html > > 3) StdbMysqlProtocol project: This is the underlying MySQL protocol driver, > and used by the MySQL API implementation > URL: http://www.squeaksource.com/StdbMysqlProtocol.html > > There is a package load ordering dependency (documented in the MySQL > implementation project). Please load the core and the protocol driver > packages first, before you load the implementation package. > > Combined, the packages has around 200 tests (most of them in the protocol > driver and the API implementation) and are running green on Pharo 1.1.1 one > click, Squeak 4.2 one click, Squeak 3.10 (with Seaside 2-8-573 dev image) > under Mac OS X 10.5.8 with MySQL server 5.0.67. > > This was in the making for some time; and I feel it is time to share it > with the community. I will continue to post more documentation and code > snippets in the project page Wiki sections. For now, looking up the tests > may be your best guide. > > Happy programming! > > Best, > Anindya Haldar > > > > > > > > > -- > Mariano > http://marianopeck.wordpress.com > > > > -- Mariano http://marianopeck.wordpress.com

Sept. 29, 2011

Re: [Pharo-users] [squeak-dev] Now available: a database conectivity API and its MySQL implementation

by Anindya Haldar

Hi Mariano, A couple of things with some history can perhaps explain this a bit better. - This all started almost a couple of years ago, when I was looking for a JDBC/DBI style API with MySQL support. - There was a MySQL driver, although a bit dated, and it lacked certain features I thought would be pretty compelling to have. - At that time I was not aware of OpenDBX, and even today I know very little about it. That is not a reflection on OpenDBX, it is my own limitation - I always wished for a rich, consistent database API with native Smalltalk drivers in Squeak/Pharo. - Since the protocol driver talks MySQL packets, and it should be possible to implement the DBXTalk API on top of it, in the same way the StdbMysqlImpl implements StdbCore API on top of the protocol driver. You may have noticed that the protocol driver is a separate project, and should be usable by any other projects for implementing another type/style of driver API I fully recognize your point here. I do wish all success to the DBX project. In my case it was just some long-drawn ans slow personal effort that I thought the result might be useful to the community. Best, Anindya ________________________________ From: Mariano Martinez Peck <marianopeck(a)gmail.com> To: Anindya Haldar <anindya_haldar(a)yahoo.com>; "pharo-users(a)lists.gforge.inria.fr" <pharo-users(a)lists.gforge.inria.fr> Sent: Thursday, September 29, 2011 1:25 AM Subject: Re: [squeak-dev] Now available: a database conectivity API and its MySQL implementation Hi Anindya. Nice to hear more effort on this front. Is there any particular reason of spending all this amount of work consider we already have DBXTalk? wouldn't be better to improve the former? DBXTalk is exactly the same, and it is already working with Oracle, MySQL, PostgreSQL, SQL Server, Sqlite3, Sybase, etc. The main problem is that we depend on an external library like OpenDBX. I guess you are using a native connection with sockets. Moreover, we have ported Glorp and adapt it to use DBXTalk driver. What I mean is that we can join forces. For example, if you did an implementation of the MySQL natively (if fact, there is already one in squeaksource although it is a little bit outdated), we could try to make the same API as DBXTalk. That way, still with the same API we can use your driver. And you can use Glorp with your driver as well. Cheers On Thu, Sep 29, 2011 at 10:11 AM, Anindya Haldar <anindya_haldar(a)yahoo.com> wrote: I am extremely pleased to offer to the community a generic Smalltalk API for database connectivity API, along with a MySQL implementation written from ground up. Think of JDBC and DBI like interfaces in other languages and environments, and this one offers abstract facilities like connection, prepared statement, resultset, row, metdata and so on for the application. > > > >The API implementation uses driver delegates, and insulates the applications from the driver specific interfaces. As of now, a MySQL implementation is available, with other databases engine supports in the future plans. >The API supports server side prepared statements and cursor based fetch implemented in the MySQL driver. > >The implementation is currently available in 3 parts: > >1) StdbCore project: This is primarily the API definitions and the delegation logic >URL: http://www.squeaksource.com/StdbCore.html > >2) StdbMysqlImpl project: This is the MySQL implementation of the StdbCore API >URL: http://www.squeaksource.com/StdbMysqlImpl.html > >3) StdbMysqlProtocol project: This is the underlying MySQL protocol driver, and used by the MySQL API implementation >URL: http://www.squeaksource.com/StdbMysqlProtocol.html > >There is a package load ordering dependency (documented in the MySQL implementation project). Please load the core and the protocol driver packages first, before you load the implementation package. > >Combined, the packages has around 200 tests (most of them in the protocol driver and the API implementation) and are running green on Pharo 1.1.1 one click, Squeak 4.2 one click, Squeak 3.10 (with Seaside 2-8-573 dev image) under Mac OS X 10.5.8 with MySQL server 5.0.67. > >This was in the making for some time; and I feel it is time to share it with the community. I will continue to post more documentation and code snippets in the project page Wiki sections. For now, looking up the tests may be your best guide. > >Happy programming! > >Best, >Anindya Haldar > > > > > > -- Mariano http://marianopeck.wordpress.com

Sept. 29, 2011

Re: [Pharo-users] About the Pharo CogVM

by StÃ©phane Ducasse

Tx! On Sep 29, 2011, at 3:35 PM, Sven Van Caekenberghe wrote: > 99% of the mails on this list are about issues, problems or feature requests, not this one. > > I did a new clean server deploy this week and decided to use the new VM as currently advertised on the downloads page, CogVM-Unix-13307, that I presume came from the CI system. I am using a 1.3 image with Seaside 3. > > $ ./coglinux/CogVM -version > 3.9-7 #1 Wed Aug 31 14:50:51 CEST 2011 gcc 4.1.2 > Croquet Closure Cog VM [CoInterpreter VMMaker-oscog-IgorStasenko.123] > Linux pharo-build.lille.inria.fr 2.6.18-194.26.1.el5xen #1 SMP Tue Nov 9 14:13:46 EST 2010 i686 i686 i386 GNU/Linux > plugin path: /home/ubuntu/coglinux/ [default: /home/ubuntu/coglinux/] > > I am happy to report that all went well: the CogVM distro is small and clean, and performed perfectly building new images and running the application server code. FYI, the server I am using is an Amazon EC2 micro instance with Ubuntu 11.04 32-bit. > > Thanks a lot ! > > Sven > > PS: I do think the VM could use some more branding here and there, especially the Mac one, but that is another story.

Sept. 29, 2011

Re: [Pharo-users] Now available: a database conectivity API and its MySQL implementation

by Anindya Haldar

Thanks Andreas. The MySQL protocol is a native all-Smalltalk MySQL driver. There is no FFI or plugin associated with it. The driver implements the MySQL wire protocol on top of socket stream. Best, Anindya ________________________________ From: Andreas Raab <andreas.raab(a)gmx.de> To: Anindya Haldar <anindya_haldar(a)yahoo.com>; The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org> Sent: Thursday, September 29, 2011 1:22 AM Subject: Re: Now available: a database conectivity API and its MySQL implementation Very nice. Quick question: How are you accessing the MySQL db? Are you using a network connection or some FFI facilities? If you are using a network connection, we might have use for your project right away; our current FFI based ODBC implementation causes headaches when the calls take a long time (>1sec). Cheers, Â - Andreas On 9/29/2011 10:11, Anindya Haldar wrote: > I am extremely pleased to offer to the community a generic Smalltalk API > for database connectivity API, along with a MySQL implementation written > from ground up. Think of JDBC and DBI like interfaces in other languages > and environments, and this one offers abstract facilities like > connection, prepared statement, resultset, row, metdata and so on for > the application. > > The API implementation uses driver delegates, and insulates the > applications from the driver specific interfaces. As of now, a MySQL > implementation is available, with other databases engine supports in the > future plans. > > The API supports server side prepared sta tements and cursor based fetch > implemented in the MySQL driver. > > The implementation is currently available in 3 parts: > > 1) StdbCore project: This is primarily the API definitions and the > delegation logic > URL: http://www.squeaksource.com/StdbCore.html > > 2) StdbMysqlImpl project: This is the MySQL implementation of the > StdbCore API > URL: http://www.squeaksource.com/StdbMysqlImpl.html > > 3) StdbMysqlProtocol project: This is the underlying MySQL protocol > driver, and used by the MySQL API implementation > URL: http://www.squeaksource.com/StdbMysqlProtocol.html > > There is a package load ordering dependency (documented in the MySQL > implementation project). Please load the core and the protocol driver > packages first, before you load the implementation package. > > Combined, the packages has around 200 tests (most of them in the > protocol driver and the API implementation) and are running green on > Pharo 1.1.1 one click, Squeak 4.2 one click, Squeak 3.10 (with Seaside > 2-8-573 dev image) under Mac OS X 10.5.8 with MySQL server 5.0.67. > > This was in the making for some time; and I feel it is time to share it > with the community. I will continue to post more documentation and code > snippets in the project page Wiki sections. For now, looking up the > tests may be your best guide. > > Happy programming! > > Best, > Anindya Haldar > > > > >

Sept. 29, 2011

About the Pharo CogVM

by Sven Van Caekenberghe

99% of the mails on this list are about issues, problems or feature requests, not this one. I did a new clean server deploy this week and decided to use the new VM as currently advertised on the downloads page, CogVM-Unix-13307, that I presume came from the CI system. I am using a 1.3 image with Seaside 3. $ ./coglinux/CogVM -version 3.9-7 #1 Wed Aug 31 14:50:51 CEST 2011 gcc 4.1.2 Croquet Closure Cog VM [CoInterpreter VMMaker-oscog-IgorStasenko.123] Linux pharo-build.lille.inria.fr 2.6.18-194.26.1.el5xen #1 SMP Tue Nov 9 14:13:46 EST 2010 i686 i686 i386 GNU/Linux plugin path: /home/ubuntu/coglinux/ [default: /home/ubuntu/coglinux/] I am happy to report that all went well: the CogVM distro is small and clean, and performed perfectly building new images and running the application server code. FYI, the server I am using is an Amazon EC2 micro instance with Ubuntu 11.04 32-bit. Thanks a lot ! Sven PS: I do think the VM could use some more branding here and there, especially the Mac one, but that is another story.

Sept. 29, 2011

Re: [Pharo-users] Now available: a database conectivity API and its MySQL implementation

by Anindya Haldar

I have now set the projects to MIT license. Thanks for the reminder. - Anindya ________________________________ From: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> To: Anindya Haldar <anindya_haldar(a)yahoo.com>; A friendly place where any question about pharo is welcome <pharo-users(a)lists.gforge.inria.fr> Cc: "squeak-dev(a)lists.squeakfoundation.org" <squeak-dev(a)lists.squeakfoundation.org> Sent: Thursday, September 29, 2011 1:18 AM Subject: Re: [Pharo-users] Now available: a database conectivity API and its MySQL implementation thanks what is the license? Stef On Sep 29, 2011, at 10:11 AM, Anindya Haldar wrote: > I am extremely pleased to offer to the community a generic Smalltalk API for database connectivity API, along with a MySQL implementation written from ground up. Think of JDBC and DBI like interfaces in other languages and environments, and this one offers abstract facilities like connection, prepared statement, resultset, row, metdata and so on for the application. > > The API implementation uses driver delegates, and insulates the applications from the driver specific interfaces. As of now, a MySQL implementation is available, with other databases engine supports in the future plans. > > The API supports server side prepared statements and cursor based fetch implemented in the MySQL driver. > > The implementation is currently available in 3 parts: > > 1) StdbCore project: This is primarily the API definitions and the delegation logic > URL: http://www.squeaksource.com/StdbCore.html > > 2) StdbMysqlImpl project: This is the MySQL implementation of the StdbCore API > URL: http://www.squeaksource.com/StdbMysqlImpl.html > > 3) StdbMysqlProtocol project: This is the underlying MySQL protocol driver, and used by the MySQL API implementation > URL: http://www.squeaksource.com/StdbMysqlProtocol.html > > There is a package load ordering dependency (documented in the MySQL implementation project). Please load the core and the protocol driver packages first, before you load the implementation package. > > Combined, the packages has around 200 tests (most of them in the protocol driver and the API implementation) and are running green on Pharo 1.1.1 one click, Squeak 4.2 one click, Squeak 3.10 (with Seaside 2-8-573 dev image) under Mac OS X 10.5.8 with MySQL server 5.0.67. > > This was in the making for some time; and I feel it is time to share it with the community. I will continue to post more documentation and code snippets in the project page Wiki sections. For now, looking up the tests may be your best guide. > > Happy programming! > > Best, > Anindya Haldar > >

Sept. 29, 2011

Re: [Pharo-users] [squeak-dev] Now available: a database conectivity API and its MySQL implementation

by Mariano Martinez Peck

Hi Anindya. Nice to hear more effort on this front. Is there any particular reason of spending all this amount of work consider we already have DBXTalk? wouldn't be better to improve the former? DBXTalk is exactly the same, and it is already working with Oracle, MySQL, PostgreSQL, SQL Server, Sqlite3, Sybase, etc. The main problem is that we depend on an external library like OpenDBX. I guess you are using a native connection with sockets. Moreover, we have ported Glorp and adapt it to use DBXTalk driver. What I mean is that we can join forces. For example, if you did an implementation of the MySQL natively (if fact, there is already one in squeaksource although it is a little bit outdated), we could try to make the same API as DBXTalk. That way, still with the same API we can use your driver. And you can use Glorp with your driver as well. Cheers On Thu, Sep 29, 2011 at 10:11 AM, Anindya Haldar <anindya_haldar(a)yahoo.com>wrote: > I am extremely pleased to offer to the community a generic Smalltalk API > for database connectivity API, along with a MySQL implementation written > from ground up. Think of JDBC and DBI like interfaces in other languages and > environments, and this one offers abstract facilities like connection, > prepared statement, resultset, row, metdata and so on for the application. > > The API implementation uses driver delegates, and insulates the > applications from the driver specific interfaces. As of now, a MySQL > implementation is available, with other databases engine supports in the > future plans. > > The API supports server side prepared statements and cursor based fetch > implemented in the MySQL driver. > > The implementation is currently available in 3 parts: > > 1) StdbCore project: This is primarily the API definitions and the > delegation logic > URL: http://www.squeaksource.com/StdbCore.html > > 2) StdbMysqlImpl project: This is the MySQL implementation of the StdbCore > API > URL: http://www.squeaksource.com/StdbMysqlImpl.html > > 3) StdbMysqlProtocol project: This is the underlying MySQL protocol driver, > and used by the MySQL API implementation > URL: http://www.squeaksource.com/StdbMysqlProtocol.html > > There is a package load ordering dependency (documented in the MySQL > implementation project). Please load the core and the protocol driver > packages first, before you load the implementation package. > > Combined, the packages has around 200 tests (most of them in the protocol > driver and the API implementation) and are running green on Pharo 1.1.1 one > click, Squeak 4.2 one click, Squeak 3.10 (with Seaside 2-8-573 dev image) > under Mac OS X 10.5.8 with MySQL server 5.0.67. > > This was in the making for some time; and I feel it is time to share it > with the community. I will continue to post more documentation and code > snippets in the project page Wiki sections. For now, looking up the tests > may be your best guide. > > Happy programming! > > Best, > Anindya Haldar > > > > > > -- Mariano http://marianopeck.wordpress.com

Sept. 29, 2011

Re: [Pharo-users] Now available: a database conectivity API and its MySQL implementation

by StÃ©phane Ducasse

thanks what is the license? Stef On Sep 29, 2011, at 10:11 AM, Anindya Haldar wrote: > I am extremely pleased to offer to the community a generic Smalltalk API for database connectivity API, along with a MySQL implementation written from ground up. Think of JDBC and DBI like interfaces in other languages and environments, and this one offers abstract facilities like connection, prepared statement, resultset, row, metdata and so on for the application. > > The API implementation uses driver delegates, and insulates the applications from the driver specific interfaces. As of now, a MySQL implementation is available, with other databases engine supports in the future plans. > > The API supports server side prepared statements and cursor based fetch implemented in the MySQL driver. > > The implementation is currently available in 3 parts: > > 1) StdbCore project: This is primarily the API definitions and the delegation logic > URL: http://www.squeaksource.com/StdbCore.html > > 2) StdbMysqlImpl project: This is the MySQL implementation of the StdbCore API > URL: http://www.squeaksource.com/StdbMysqlImpl.html > > 3) StdbMysqlProtocol project: This is the underlying MySQL protocol driver, and used by the MySQL API implementation > URL: http://www.squeaksource.com/StdbMysqlProtocol.html > > There is a package load ordering dependency (documented in the MySQL implementation project). Please load the core and the protocol driver packages first, before you load the implementation package. > > Combined, the packages has around 200 tests (most of them in the protocol driver and the API implementation) and are running green on Pharo 1.1.1 one click, Squeak 4.2 one click, Squeak 3.10 (with Seaside 2-8-573 dev image) under Mac OS X 10.5.8 with MySQL server 5.0.67. > > This was in the making for some time; and I feel it is time to share it with the community. I will continue to post more documentation and code snippets in the project page Wiki sections. For now, looking up the tests may be your best guide. > > Happy programming! > > Best, > Anindya Haldar > >

Sept. 29, 2011

Now available: a database conectivity API and its MySQL implementation

by Anindya Haldar

I am extremely pleased to offer to the community a generic Smalltalk API for database connectivity API, along with a MySQL implementation written from ground up. Think of JDBC and DBI like interfaces in other languages and environments, and this one offers abstract facilities like connection, prepared statement, resultset, row, metdata and so on for the application. The API implementation uses driver delegates, and insulates the applications from the driver specific interfaces. As of now, a MySQL implementation is available, with other databases engine supports in the future plans. The API supports server side prepared statements and cursor based fetch implemented in the MySQL driver. The implementation is currently available in 3 parts: 1) StdbCore project: This is primarily the API definitions and the delegation logic URL: http://www.squeaksource.com/StdbCore.html 2) StdbMysqlImpl project: This is the MySQL implementation of the StdbCore API URL: http://www.squeaksource.com/StdbMysqlImpl.html 3) StdbMysqlProtocol project: This is the underlying MySQL protocol driver, and used by the MySQL API implementation URL: http://www.squeaksource.com/StdbMysqlProtocol.html There is a package load ordering dependency (documented in the MySQL implementation project). Please load the core and the protocol driver packages first, before you load the implementation package. Combined, the packages has around 200 tests (most of them in the protocol driver and the API implementation) and are running green on Pharo 1.1.1 one click, Squeak 4.2 one click, Squeak 3.10 (with Seaside 2-8-573 dev image) under Mac OS X 10.5.8 with MySQL server 5.0.67. This was in the making for some time; and I feel it is time to share it with the community. I will continue to post more documentation and code snippets in the project page Wiki sections. For now, looking up the tests may be your best guide. Happy programming! Best, Anindya Haldar

Sept. 29, 2011

Re: [Pharo-users] A small problem with ScaledDecimal

by Larry White

On Tue, Sep 27, 2011 at 7:44 AM, Davorin Rusevljan < davorin.rusevljan(a)gmail.com> wrote: > On Tue, Sep 27, 2011 at 1:37 PM, Larry White <ljw1001(a)gmail.com> wrote: > > Hi, I had a need to replace the printOn: implementation in ScaledDecimal > so > > that it didn't include the scale. In other words, I don't want my users > to > > see '3.02s2'. Being lazy, my first impulse was to remove the code from > > printOn: that appends the scale, but I realized I'd have to do that every > > time I upgraded my pharo version. > > Instead I tried to implement a subclass called DisplayableScaledDecimal > and > > override printOn. That seems straightforward and smalltalky, but when I > do > > math on instances of DisplayableScaledDecimal, the results are converted > > back to ScaledDecimal. Now I'm looking at re-implementing all the math > > logic in scaledDecimal to avoid that. > > The problem seems to be in the coerce: method, which reads: > > coerce: aNumber > > "Note: this quick hack could be replaced by double dispatching" > > aNumber class = self class ifTrue: [^self class newFromNumber: aNumber > > scale: (scale max: aNumber scale)]. > > (aNumber isFraction or: [aNumber isInteger]) ifTrue: [^self class > > newFromNumber: aNumber scale: scale]. > > ^aNumber > > I guess I could override coerce:, but that seems wrong. > > So my question to the smalltalk gods on the list is: Could this be fixed > > with double dispatching as the comment sort of suggests, and would it be > a > > useful thing to do? > > hm not sure about that. > > It is usually a good idea that Smalltalk can read object from > representation that is outputed from #printOn: , and loosing a scale > in #printOn: seems to defeat that rule of the thumb. > I appreciate the heads-up, but the comment for storeOn: says that storeOn: should be used for storage because printOn: can lose precision. I guess maybe I misunderstood the intent here (time to check the blue book) but I thought storeOn: was for machines and printOn: for humans, roughly speaking. FWIW, I think the rule of thumb that says "programs should be written to be read by human's first and computers second" is violated by having the standard display for a simple decimal number include the scale. as an aside: I just watched an old video where Dan Ingalls shows how easy it is to override a numeric type in Smalltalk and just implement the methods that differ. But that was before ScaledDecimal was around. ;) But I think you're generally right about this and I was fighting against the language implementation, so I implemented a couple of String constructors that take and format scaled decimals and will scatter them throughout my ui. It's no worse than formatting dates I guess. thanks. > So maybe avoiding messing with #printOn: is better idea, and > introducing a message of your own that converts to the format you wish > is a better way. > Just my 2c > > Davorin Rusevljan > http://www.cloud208.com/ > >

Sept. 27, 2011