×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
However please don't let something like this go into production.
I don't even want to imagine life as a programmer where code that's not explicitly commented out may be implicitly (if that's the right word) commented out due to a compiler directive was resulting in code not being included in a program. To think every time you were making changes you'd have to look for compiler directives first. Ugh.
For testing purposes, I do understand doing something like this.
Although honestly I tend to do a less savory thing: delete. Save. Compile. Undo. Save.
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of blayman@xxxxxxxxxxxxxxx
Sent: Friday, July 24, 2009 1:25 PM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Block Commenting in LPEX
Yes, it will, below is an example of a compile listing using the
DEFINED(SKIP). This isn't what it was designed for but it works to comment
out a bunch of lines of code.
865 C EOM IFEQ 'Y'
866 C/if defined(skip)
LINES EXCLUDED: 10
867 C/endif
868 C ARSTOR IFEQ *BLANK
869 C MOVE *BLANKS F1SEQ
From:
Bryce Martin <BMartin@xxxxxxxxxxxx>
To:
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
Cc:
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>,
wdsci-l-bounces@xxxxxxxxxxxx
Date:
07/24/2009 02:16 PM
Subject:
Re: [WDSCI-L] Block Commenting in LPEX
Sent by:
wdsci-l-bounces@xxxxxxxxxxxx
And the compiler will ignore it no matter what is in there?
Thanks
Bryce Martin
Programmer/Analyst I
570-546-4777
blayman@xxxxxxxxxxxxxxx
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
07/24/2009 01:46 PM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
To
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
cc
Subject
Re: [WDSCI-L] Block Commenting in LPEX
You can comment blocks of code in RPGIV you just need to add a /IF
DEFINED(SKIP) to the first line then at the end of the block add a /ENDIF
you will skip all the code between the /IF and /ENDIF
From:
Bryce Martin <BMartin@xxxxxxxxxxxx>
To:
"'wdsci-l@xxxxxxxxxxxx'" <wdsci-l@xxxxxxxxxxxx>
Date:
07/24/2009 01:40 PM
Subject:
[WDSCI-L] Block Commenting in LPEX
Sent by:
wdsci-l-bounces@xxxxxxxxxxxx
I know that you can't do block commenting in RPGIV (at least that I'm
aware of), so is there something in LPEX that will help me comment out
large blocks of code quickly without having to put a asterick on each
line?
Thanks
Bryce Martin
Programmer/Analyst I
570-546-4777
--- This message (including any attachments) is intended only for the use
of the individual or entity to which it is addressed and may contain
information that is non-public, proprietary, privileged, confidential, and
exempt from disclosure under applicable law. If you are not the intended
recipient, you are hereby notified that any use, dissemination,
distribution, or copying of this communication is strictly prohibited. If
you have received this communication in error, please notify us and
destroy this message immediately. ---
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.