|
I think expanding /COPY statements inside the editor might be more complicated than you thing, since yoiu would also have to honor conditional directives. For example, this snippet is just a bit of a larger source member that contains the code of the module. /if not defined(CopyingPrototypes) .... code /endif * DGetCoast PR 1A D #LOC 4S 0 * /if defined(CopyingPrototypes) /eof /endif ... much more code... but is used to copy in the prototype from the original source, with code like this: /define CopyingPrototypes /copy getcoast /undefine CopyingPrototypes Note that I'm not necessarily recommending this, but it would have to be accounted for, otherwise you'd get a whole lot of source you didn't want. Sam >From: "August Fassler" <AUGUST.FASSLER@xxxxxxxxxxx> >Reply-To: Websphere Development Studio Client for iSeries<WDSCI-L@xxxxxxxxxxxx> >To: "Websphere Development Studio Client for iSeries" <WDSCI-L@xxxxxxxxxxxx> >Subject: RE: [WDSCI-L] Prototypes & /copy >Date: Wed, 10 Mar 2004 15:41:17 -0600 > >Thanks Greg. I was hoping that there might be a bit more of an >"integrated" approach. I was aware that it could be opened in its own >tab - the shortcuts to the source are nice, but I'd love to be able to >actually view the copied source as a component of the source member I'm >editing. > >I understand that /copy is a "compiler directive" - but, hey we're using >a souped-up editor here...how about a few more steroids for it? >Obviously, expanding the copied source would entail a momentary >performance hit - approximately the same as opening it in its own tab, I >would think??? > >Oh well...back I go, to the search for the golden /copy... > >August > > >-----Original Message----- >From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] >On Behalf Of Gregg Willow >Sent: Wednesday, March 10, 2004 3:24 PM >To: Websphere Development Studio Client for iSeries >Subject: Re: [WDSCI-L] Prototypes & /copy > > >August, > >Double-click the copy member text. It will highlight the source file and >the member. Then, click Source->/Copy member->Edit or Browse. It will >open the source under a new tab. I really like this option. > >Best regards, > >Gregg Willow >Programmer/Analyst >Minnesota Counties Information Systems >413 SE 7th Avenue >Grand Rapids, MN 55744 >218-326-0381 ext: 17 >gregg.willow@xxxxxxxxxxxxxx >----- Original Message ----- >From: "August Fassler" <AUGUST.FASSLER@xxxxxxxxxxx> >To: "Websphere Development Studio Client for iSeries" ><WDSCI-L@xxxxxxxxxxxx> >Sent: Wednesday, March 10, 2004 2:32 PM >Subject: [WDSCI-L] Prototypes & /copy > > >I've only recently begun to play with service programs and procedures, >etc... I have noticed that many sources of information regarding >prototypes appear to strongly recommend using copy source rather than >copying the prototype directly into your program. This raises an >interesting issue for me. We have all but said never, ever use copy >source. This is due to the fact that you can't scan for its contents >within a program and that you can't see its contents while programming. > >I'm not nearly as concerned about scanning source for it as I am that I >can't see what I'm working with when coding. Is there a way to "expand" >the copy source within the source editor in WDSC? I noticed that the >definitions DO show up in the outline view, but the only option I appear >to have as far as viewing the actual source is to open the source in its >own window. > >If we're talking new feature, what I'd like to see is this.... In a >manner similar to filtering, show a "+" to the left of the /copy >statement. If I click on the "+", expand it into the current view. The >expanded source would really need to be protected - perhaps in a >different color. > >Also, any advice on how best to manage/view binding directories from >within WDSC would be greatly appreciated...new blood here, when it comes >to this...ahhh, but having fun, nonetheless! > >August Fassler >Lead Programmer/Analyst >Sporlan Valve Company > > >_______________________________________________ >This is the Websphere Development Studio Client for iSeries (WDSCI-L) >mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, >unsubscribe, or change list options, >visit: http://lists.midrange.com/mailman/listinfo/wdsci-l >or email: WDSCI-L-request@xxxxxxxxxxxx >Before posting, please take a moment to review the archives >at http://archive.midrange.com/wdsci-l. > >_______________________________________________ >This is the Websphere Development Studio Client for iSeries (WDSCI-L) >mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, >unsubscribe, or change list options, >visit: http://lists.midrange.com/mailman/listinfo/wdsci-l >or email: WDSCI-L-request@xxxxxxxxxxxx >Before posting, please take a moment to review the archives >at http://archive.midrange.com/wdsci-l. > >_______________________________________________ >This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list >To post a message email: WDSCI-L@xxxxxxxxxxxx >To subscribe, unsubscribe, or change list options, >visit: http://lists.midrange.com/mailman/listinfo/wdsci-l >or email: WDSCI-L-request@xxxxxxxxxxxx >Before posting, please take a moment to review the archives >at http://archive.midrange.com/wdsci-l. ---------------------------------------------------------------------- Frustrated with dial-up? Lightning-fast Internet access for as low as $29.95/month.
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.