Article View: comp.os.os2.programmer
Article #724Re: I have some questions.. (nobody had answered)..
From: Barry King
Date: Thu, 16 Apr 1992 01:26
Date: Thu, 16 Apr 1992 01:26
132 lines
3141 bytes
3141 bytes
OPRJ36@TREARN.BITNET (Bahri Bora BALI AG) writes:
>1. Is there a good text editor running under OS/2 1.3? If so,
> how can I get it?
There are several. Most are available from various software
mail order house such as Programmer's Connction or Programmer's
Paradise.
Brief 3.1 Solution Systems
- OS/2 and DOS versions. Character mode.
- powerful, fully configurable, popular
- comes with awk-like macro language
SageEdit Intersolv (merged with Sage Software)
- OS/2, DOS and dual mode
- character based
- awk-like macro language
- very powerful, fully configurable
MultiEdit, QEdit, Epsilon, Edix, Edix/GS are others.
Of interest to mainframe types might be Mansfield's (?)
KEdit (like XEdit on VM/CMS) and SPF/2 like the MVS/TSO
ISPF editor.
>2. Someone had told me that there is a paper documentation about
> use of PM functions in REXX. If still so, how can I get it?
> And I had heard that there is a help file named REXX.INF?
> True? If so, can I get it? Of course, from where?
This information comes with IBM's Programming Tools and Information
kit. You can also download REXX .INF files from Compuserve or
major OS/2 BBSs.
>3. I hate COBOL but here, programmers want to write with
> it. Do you have sample codes in COBOL/2, using
> PM functions or OS/2 Service Calls? If so, *8) will
> you send them to me?
COBOL, as an SAA language, is supported for OS/2 and PM development.
Examples come with the IBM PT&I kit. It's a pain in the butt, IMHO,
to code PM in COBOL. Anything in COBOL, actually, but with OS/2
it just doesn't seem to be very 'natural'...
>4. In these networks, with WHICH NODE/SITE sould I contact to
> discuss something about IBM's FBSS/2?
Dunno.
>5. Is it possible to develope Device Drivers for OS/2, by
> programming in COBOL/2? Here, programmers are asking
> about this.
Probably, but you'd still need some assembler and C to get the
beast up. Again, COBOL is simply not an appropriate choice
for systems level development. Why not just take a couple
of hot-shots and let them loose with C? After all, it isn't
magic - it's just another (very powerful) programming language.
>Thank you for your interest.. Kind regards..
hope this helps.
(sorry about the crappy formatting...)
Barry King bking@ersys.edmonton.ab.ca
Edmonton Remote Systems: Celebrating 10 years of service to Northern Alberta
Technical Details
Message-ID:
<J8uaJB1w164w@ersys.edmonton.ab.ca>Path:
arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!van-bc!ubc-cs!alberta!ugc!ersys!bkingReferences:
<92100.131804OPRJ36@TREARN.BITNET>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!van-bc!ubc-cs!alberta!ugc!ersys!bking From: ersys!bking@agchem.redwater.iol.ca (Barry King) Newsgroups: comp.os.os2.programmer Subject: Re: I have some questions.. (nobody had answered).. Message-ID: <J8uaJB1w164w@ersys.edmonton.ab.ca> Date: Wed, 15 Apr 92 19:26:54 MDT References: <92100.131804OPRJ36@TREARN.BITNET> Organization: Edmonton Remote Systems, Edmonton, AB, Canada Lines: 132