|
>I take it the key phrase here is "fr those who know how to use it". Absolutely. Just like any other tool. If I want to know how to use an API, I have to RTFM. Yes, I realize many programmers avoid the cycle at all costs. That's too bad. At the risk of sounding like a heretic, there *are*, IMHO, still good reasons for using the cycle. If you want to go through the bother of rolling your own level break code, go for it. While you're still coding, I'll be testing. As for maintainability after I leave a shop, my gosh, aren't level breaks still documented? I think so. RTFM, it's not that hard to understand. Please understand, I've been out of S/36 since the 400's debut, I was using full-procedural files since the day it was introduced on the S/36. I am not stuck on the cycle. Use the tools that are available. If I had legal access to source like JDEdward's S002 subroutine (you're getting the idea I like this marvel of code?!?), I'd probably swear off RPG's level break processing in a minute. Mike, do you have a template for your DIY level break code that you could share? - Dan Bale (I am *NOT* "Dale" http://archive.midrange.com/midrange-l/200105/msg00281.html ) SAMSA, Inc. 989-790-0507 DBale@SAMSA.com <mailto:DBale@SAMSA.com> Quiquid latine dictum sit altum viditur. (Whatever is said in Latin seems profound.)
As an Amazon Associate we earn from qualifying purchases.
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.