I have enhanced assembler language syntax with respect to the rules
governing continuation and commentary. Unfortunately, ISPF's edit
highlighting and colorization doesn't understand these enhancements.
Is it possible to create a custom edit highlighting program? If so, how?
BTW, I found ISP.SISPSAMP(ISRPXASM), but that's just keywords.
--
.-----------------------------------------------------------------.
| Edward E. Jaffe | |
| Mgr, Research & Development | edj...@phoenixsoftware.com |
| Phoenix Software International | Tel: (310) 338-0400 x318 |
| 5200 W Century Blvd, Suite 800 | Fax: (310) 338-0801 |
| Los Angeles, CA 90045 | http://www.phoenixsoftware.com |
'-----------------------------------------------------------------'
What exactly do you mean by "I have enhanced assembler language syntax with respect to the rules governing continuation and commentary."?
HI ASM does a lot of this (or HI AUTO as long as there is an "*" in column 1).
I think this has been covered before and the answer from "somebody" was basically "no". If I recall, "somebody" said that a panel exit could be used as a kinda-sorta customization but you'd have to look up more specifics on this.
--
Jim Moore
Concentrated Logic Inc
The "someone" would have been me. I haven't tried it so I don't know for
sure, but I'm reasonably confident someone could create their own customized
highlighting routine by coding something that would be called as a panel
exit in the INIT routine.
Dave Salt
SimpList(tm) - The easiest, most powerful way to surf a mainframe!
http://www.mackinney.com/products/SIM/simplist.htm
>What exactly do you mean by "I have enhanced assembler language syntax with respect to the rules governing continuation and commentary."?
>
>
Traditional assembler syntax rules require that comment lines have an
asterisk in column 1, continuation characters appear in column 72, and
continued statements begin in column 16. Those are the rules ISPF's
assembler language highlighting code is enforcing. That behavior is
precisely what I want to change.
>HI ASM does a lot of this (or HI AUTO as long as there is an "*" in column 1).
>
>I think this has been covered before and the answer from "somebody" was basically "no". If I recall, "somebody" said that a panel exit could be used as a kinda-sorta customization but you'd have to look up more specifics on this.
>
>
That's unfortunate. I don't think a panel exit can reliably do what I
want. Depending on how the edit session is positioned, the exit won't be
able to necessarily see all parts of a multi-line, continued statement
in the source.
Are ISPF services allowed from within a panel exit?
--
-----------------------------------------------------------------
Actually, I was alluding to Doug Nadel whose code name used to be "somebody". Doug did a presentation on ISPF color highlighting at a Share conference before it became a part of stock ISPF.
I had the same question Ed Jaffe had a few years ago and Doug pointed me to a Share web site that still had his presentation posted.
I'm not sure if it's still there as this was already a number of years ago.
--
Jim Moore
Concentrated Logic Inc
-------------- Original message --------------
> Jim,
>
> The "someone" would have been me. I haven't tried it so I don't know for
> sure, but I'm reasonably confident someone could create their own customized
> highlighting routine by coding something that would be called as a panel
> exit in the INIT routine.
>
> Dave Salt
> SimpList(tm) - The easiest, most powerful way to surf a mainframe!
> http://www.mackinney.com/products/SIM/simplist.htm
>
>
>
>
>
> >From: JB Moore
> >Reply-To: ISPF discussion list
> >To: ISP...@listserv.nd.edu
> >Subject: Re: Customized Edit Highlighting
> >Date: Sat, 8 Oct 2005 21:51:45 +0000
> >
> >Ed,
> >
> >What exactly do you mean by "I have enhanced assembler language syntax with
> >respect to the rules governing continuation and commentary."?
> >
> >HI ASM does a lot of this (or HI AUTO as long as there is an "*" in column
> >1).
> >
> >I think this has been covered before and the answer from "somebody" was
> >basically "no". If I recall, "somebody" said that a panel exit could be
> >used as a kinda-sorta customization but you'd have to look up more
> >specifics on this.
> >
> >--
> >Jim Moore
> >Concentrated Logic Inc
> >
> >-------------- Original message --------------
> >
> > > Hello,
> > >
> > > I have enhanced assembler language syntax with respect to the rules
> > > governing continuation and commentary. Unfortunately, ISPF's edit
> > > highlighting and colorization doesn't understand these enhancements.
> > >
> > > Is it possible to create a custom edit highlighting program? If so, how?
> > >
> > > BTW, I found ISP.SISPSAMP(ISRPXASM), but that's just keywords.
> > >
> > > --
> > > .-----------------------------------------------------------------.
> > > | Edward E. Jaffe | |
> > > | Mgr, Research & Development | edj...@phoenixsoftware.com |
> > > | Phoenix Software International | Tel: (310) 338-0400 x318 |
> > > | 5200 W Century Blvd, Suite 800 | Fax: (310) 338-0801 |
> > > | Los Angeles, CA 90045 | http://www.phoenixsoftware.com |
> > > '-----------------------------------------------------------------'
>Actually, I was alluding to Doug Nadel whose code name used to be "somebody". Doug did a presentation on ISPF color highlighting at a Share conference before it became a part of stock ISPF.
>I had the same question Ed Jaffe had a few years ago and Doug pointed me to a Share web site that still had his presentation posted.
>I'm not sure if it's still there as this was already a number of years ago.
Hi Ed. I don't (intentionally) subscribe to this list anymore so I hope you will get
this. Jim is right, there is no way to influence the behavior of the hilight stuff
because each one is just hard coded. And you are correct too (of course) that the panel
exit solution is limited because you can't get access to lines that are off the screen so
that multi-line statements and comments can't easily be handled. You could do some
caching, but that would not know of changes from things like change commands and has many
otherlimitations.
That having been said though, an updated version of the highlight stuff Jim mentioned is
available at http://www.sillysot.com/ftp in the file hibrowse.panel. It is a panel that,
when used as a PANEL() on the BROWSE command, will highlight Rexx code. It uses the
inline Rexx panel exits available in ISPF 1.6 (?).
Use: download it to ISPPLIB (or use LIBDEF) and invoke BROWSE with PANEL() name
-Doug (formerly somebody@mindsp.. oh you know)
I've used panel exits for many different reasons, but never for trying to
create my own edit highlighting. I don't see any reason it couldn't be done,
but I've never had a reason to try it.
Dave Salt
SimpList(tm) - The easiest, most powerful way to surf a mainframe!
http://www.mackinney.com/products/SIM/simplist.htm
>From: "Edward E. Jaffe" <edj...@PHOENIXSOFTWARE.COM>
>Reply-To: ISPF discussion list <ISP...@listserv.nd.edu>
>To: ISP...@listserv.nd.edu
>Subject: Re: Customized Edit Highlighting
It sounded like you were refering to the message I sent to the ISPF listserv
on Aug 24 2004 in which I responded to a question posted by Thomas Berg. The
subject of the post was "MSGLINEs, NOTELINE with other colors etc..." and
Thomas asked "I'm wondering if it's possible to create something like a
customized version of NOTELINE/MSGLINE etc. as in "LINE_AFTER .XXXX =
NOTELINE (datavar)".
I responded by saying "you might be able to accomplish what you want using a
panel
exit. In this case, the INIT section of the panel would pass the ZDATA and
ZSHADOW variables to a panel exit. The panel exit would look for a NOTELINE
or MSGLINE appearing in ZDATA. If it found one, it would set the
corresponding area of ZSHADOW to whichever attribute character you wish to
use".
But as I said then (and as I say now) it's all just speculation on my part
as I've never had any reason to try it. I'm quite sure that "someone" would
know for sure :-)
Dave Salt
SimpList(tm) - The easiest, most powerful way to surf a mainframe!
http://www.mackinney.com/products/SIM/simplist.htm
>From: JB Moore <conl...@COMCAST.NET>
>Reply-To: ISPF discussion list <ISP...@listserv.nd.edu>
I have a little example of what Dave was suggesting and will post it if anyone is interested in seeing it. I did it a while back just to see if I could.
So it does work, but this method is limited to the data you can see in ZDATA. So if you wanted to match brackets, you wouldn't be able to as you only see the window image of the data you are editing and you don't have access to the edit functions.
I was going to provide some custom highlighting using this method, but there really isn't enough information passed to the panel exit to do it properly.
Bruce Schaefer
Senior Architect
Vanguard Integrity Professionals
Jim,
PLEASE JOIN US AT OUR 20th ANNUAL
ENTERPRISE/RACF SECURITY TRAINING
CONFERENCE AND EXPOSITION!
July 8 - July 12, 2006
San Diego, California
Register Today www.go2vanguard.com/expo
thinkSecurity
thinkVanguard
This e-mail and any attachments are intended solely for the use of the addressee and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination of this e-mail or any attachments is strictly prohibited. If you have received this e-mail in error, please delete all copies of this e-mail and any attachments and notify the sender immediately. Thank you.
I have raised a Design Change Request with the ISPF team to make the
Edit HiLite a bit more flexible. Obviously there is no guarantee that
the request will be accepted - but I live in hope.
Here is the text of the request :
Description:
EDIT HILITE enhancements for HLASM. Add support for structured HLASM
as presented by Ed Jaffe at recent SHARE conference where the required
syntax for things like continuation lines are relaxed. The main syntax
elements involved are as follows:
-Comment blocks may start in any column. They may begin with
an asterisk (*) or a slash and asterisk (/*). Allows comment
indentation to match that of the code.
-No explicit continuation needed when macro operand ends with
trailing comma.
-Continued macro operands may start in any column.
Requirement Type:
Ease of Use
Suggested Solution:
Provide a keyword in ISPF Configuration file for HILITE - using
structured HLASM that allows user to specify they would like to follow
the relaxed syntax as outlined in structure HLASM presentation from
SHARE.
Rob Scott
Rocket Software
www.rs.com