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



I am not sure what you mean by a crappy implementation. One line to define the file to be used seems fairly simple to me.

Of course, too, remember that the target audience for VARPG is RPG programmers, not UNIX gurus or c++ programmers. So, making it like UNIX or c++ is not a goal for VARPG. If someone wants to use UNIX or c++, by all means, do so. No reason not to. But please don't obfuscate how I make a living in the process.

You may like the idea that RPG is beginning to look like every other language, but many RPG programmers don't see the big advantage of mucking up what has worked well for a very long time.



Larry Ducie wrote:
Hi Rob,
...
IMHO, if we are going to get into the habit of using file descriptors then
we need to use them "properly". By that I mean we need to follow the already
well-trodden Win32/unix/linux route. To implement it as some unholy F-spec
b*stard-child was a big mistake. (again, IMHO). VARPG should have natively
implemented support for open(), close(), etc.. without any F-spec nonsence.
....
I like the way RPG is becoming less like the estranged relative, and is
coming into the fold. I like that I can read a nice bit of C code and think
"that would work really well, if not better, in RPG". I just couldn't do
that if RPG constantly insisted on doing it's own thing.
Just my thoughts. Larry Ducie



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.