Randy, You are making a valid point. There are many aspects of software development which can be affected by change, for better or for worse. I was talking about the problem of using an API, which is the topic of this thread. These approches work on the level of modular units, such as components. Argument names are syntactical aspects of the language. There are different approaches to handle that. In particular, search and replace of the source code worked very well on all the source of J libraries just between two beta releases. So that's even a simpler task.
----- Original Message ---- From: Randy MacDonald <[EMAIL PROTECTED]> To: Programming forum <[email protected]> Sent: Saturday, June 24, 2006 11:38:46 PM Subject: Re: [Jprogramming] Grid API Usability Hello Oleg; Does this approach work for the y. -> y change? I didn't think so. ------------------------------------------------------------------------ |\/| Randy A MacDonald | APL: If you can say it, it's done.. (ram) |/\| [EMAIL PROTECTED] | |\ | |If you cannot describe what you are doing BSc(Math) UNBF'83 þas a process, you don't know what you're doing. Sapere Aude | - W. E. Deming Natural Born APL'er | Demo website: http://156.34.78.239/ -----------------------------------------------------(INTP)----{ gnat }- ----- Original Message ----- From: "Oleg Kobchenko" <[EMAIL PROTECTED]> To: "Programming forum" <[email protected]> Sent: Saturday, June 24, 2006 11:55 PM Subject: Re: [Jprogramming] Grid API Usability That's a very good point. The solution is to protect your application code from the library implementation, using an isolation layer. A good API usually has such public immutable interface which wraps arround the private concrete implementation. That's how C runtime library and OpenGL work as examples. J wd is almost like that between platforms. However, there are instances where the same application needs to use different API's even in the same version, for example, OpenGL and DirectX. Then such isolation is written in the application, typically called façade. Then if you need to accommodate for a different APIs, the changes are made in that small portion all in one place, rather then scattered all around code, as in a monolithic application. In case of grid, there is much improvement in the totally new control. The interface is easier and functionality is more powerful. So instead of finding the common layer between them it should be easier just to "port" your code to the new interface. It would be easier if you collected all grid calls in one place while still in J504 and then just rewirte that small piece. ----- Original Message ---- From: Andrew Nikitin <[EMAIL PROTECTED]> To: [email protected] Sent: Saturday, June 24, 2006 10:05:57 PM Subject: [Jprogramming] Grid API Usability >Date: Fri, 23 Jun 2006 16:48:10 -0700 (PDT) >From: Oleg Kobchenko <[EMAIL PROTECTED]> > >I would like to conduct a Grid API Usability test. I blew some dust off my old grid scripits and found out that all of them do not work any more. The question would be, what is the point of using grid if it is virtually guaranteed that your apps that use it will not work in the next version? ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
