× 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 Thu, 2003-10-23 at 17:19, Buck wrote:
> I believe from my experience that it is indeed possible and easy to ease
> sub-procedures into existing code a little at a time.  If a simple viola
> player like me can do it, _I_believe_ anyone can!  And I started out in the
> card age.  By the bye, Fire is cool!  Heh heh heh!  Yeah, cool!
>   --buck

I couldn't agree more: my first recommendation is to find a subroutine
that has been copied all over the place (c'mon, we've all got 'em!) 
Make a new *MODULE out of just that code, and the next time you work on
a program, replace the EXSR with the prototype /copy and a myProcedure()
call.  

Or you could download a tool library like mine and start by simply using
some of the procedures.  Little more than a RSTLIB and some /copys and
you are suddenly livin' in ILE-land.  Once you are comfortable using
them you really aren't that far from writing them.

Start there as a proof of concept and slowly work outwards.  There is
nothing saying that the old methods and the new methods can't live side
by side in harmony, but give it a couple of weeks and I bet you'll never
look back at the old methods...

And Buck, isn't "viola" french or italian for "ta-da!"?  

:-) Smiles as he warms his hands over the fire... look at the pretty
colors...

Joel
http://www.rpgnext.com 



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.