|
Scott, >The point is, if IBM says "we're no longer developing SEU" its going to >mean that in 2 or 3 releases, they'll stop distributing it, too. Then >it'll cease to exist... SEU is very unlikely to disappear. It just won't get new features now that you can create your own line commands. I suspect that even the syntax checking will get updates to recognize new HLL constructs, but enhancements beyond the current feature set will not happen. I haven't heard any rumors of dropping support for the product; just not enhancing it. (When was the last time DFU was enhanced? It is also part of ADTS but likely does not have active development. But it is still supported, and changed when necessary. For example, null field support was added, but I consider this more of a comparability issue than an enhancement.) For that matter, I wouldn't say that PDM has really changed much since V1R1 either. It is supported, but not actively enhanced more than necessary (e.g. new source types, create modules, etc). Aside from ADTS, there are numerous other program products which have a history of being supported by not enhanced, even when very widely used. I'd be surprised if Query/400 didn't have more actual users than SEU/400, but I don't see it being enhanced either. The notable exception is the announced plans to drop OV/400. >When I'm out in our production facility, and I find some minor bug in my >code, right now I can log onto a green screen terminal, fix the code and >recompile. Without SEU, I'm walking/driving back to my office... I think it is quite a stretch to imagine SEU being taken away or that you'd have to drive back to your office to edit some source. If ADTS is installed at the client, there will surely be a way to edit source. Even without ADTS installed, you could just FTP the source to a Linux machine or Mac or FreeBSD w/Gnome under XFree86 or whatever your preference. Your desktop system of choice will surely have an editor suitable for minor bug fixes, even if it doesn't have the RPG literacy of editors like CODE or Flex. For that matter, minor bug fixes could even be handled with a product like WRKDBF or DBU in a pinch. >In no way am I suggesting that Code/400 be removed -- all I'm asking is >that SEU not be abandoned. If you prefer your graphical editor, go for >it! I'm more productive in SEU, and I don't want to see it dropped. I don't think anybody is suggesting that SEU be removed. >Think to yourself: "What would I do if _my_ >favorite development tool was going to be discontinued?" I'd talk to them about licensing the source for personal use or possibly even remarketing. Admittedly, that is not a viable option for SEU. Doug +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.