× 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.



On Wed, Jun 29, 2011 at 9:03 AM, Charles Wilt <charles.wilt@xxxxxxxxx> wrote:
Not sure what you mean as you can't declare local variables twice...

Unless you're talking about parameters on the procedure interface and
prototypes...

Yes, that's what I was talking about.

I'd agree that it's a slight pain...as would IBM which is why they
removed the requirement for a PR for local procedures in 6.1 (or 7.1?)

According to someone else in this thread, it's gone in 7.1, but that
doesn't help me. ;)

Particularly with WDSCi or it's successors as
you can have multiple editable windows into the same source.  So it's
easy to have one at the bottom where the procedure is being written
and one at the top where the prototype needs to go.

See, this is the kind of thing I'm talking about where the IDE might
be able to provide enough assistance that it reduces my excuses for
avoiding use of prototypes.

Lastly, WDSCi has a "New procedure" wizard that automatically creates
the PR along with the P and PI for you.

And *this* is precisely what I was referring to by "maybe the IDE can
generate the boilerplate for me". Granted, sometimes wizards are
crap, and I would have to try it for a while before I decided whether
it was more help or annoyance. But nice to know it's there.

Seriously, if my company ever upgrades their i and provides us with
powerful enough development workstations, I do think I'll give a
full-blown IDE real consideration.

John Y.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.