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





-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of rpg400-l-request@xxxxxxxxxxxx
Sent: Tuesday, January 22, 2013 12:54 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: RPG400-L Digest, Vol 12, Issue 39

Send RPG400-L mailing list submissions to
rpg400-l@xxxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.midrange.com/mailman/listinfo/rpg400-l
or, via email, send a message with subject or body 'help' to
rpg400-l-request@xxxxxxxxxxxx

On Tue, 22 Jan 2013, 13:27:31, John Yeung wrote:

It sounds like the battle you should be fighting is not whether
free-form is better than classic RPG, but whether fewer lines of code
is always better. There are simply some things that free-form cannot
achieve in as few lines as classic (especially if you count the
D-specs required for set-up, which I think is fair when counting lines
of code), so you just have to accept those particular battles as lost.
Hopefully, the war is about overall readability and maintainability.

John

I agree that sometimes less code is not better than more readable code. I
guess something I should have added to the original post was that even
though my example was just 3-bytes long, some of the strings are somewhat
long (up to 15 in a few cases).

But, the upshot is that now I can talk to my colleagues about basing
pointers!

Buzz



As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.