Re: RPG 400 code on the NET

I agree.  Back when I was programming in Quick Basic I was much more
apt to pay someone for a library if it came with source code.  99% of the
time I never changed the source code, but a lot of times it is the only way
to really understand what a routine is doing.  As you can tell, I don't much
like the black box theory, unless I can open it up and peer inside.

Regards,

Jim Langston

pcunnane@learningco.com wrote:

>      "What we need is an EXAMPLE library that can be downloaded and
>      searched."
>
>      Sounds to me like wheel-reinventing.  Besides, the whole point of
>      code-sharing is that if you don't like the way a library is
>      implemented, you can change it to suit yourself.  If you think the
>      change improves the library, share it back out.
>
>      I realise that this approach doesn't suit all shops, but look at it
>      this way - if you get a service program, complete with source code,
>      then you automagically *get* an example library.  The important
>      difference is that the example library has been subjected to extensive
>      peer review, and proven to work in other installations.  Hopefully.
>
>      "Hell that would be building another Microsoft Windows environment.
>      Lots of DLL to use and no way to see if they have bugs."
>
>      Au contraire, the single biggest problem with Windows is the fact that
>      the source code is closed.  I *strongly* advocate the publication of
>      source code with libraries, for the precise purpose of being able to
>      find the bugs.  The DLL concept is one of the (few) strengths of
>      Windows, and it warmed my heart to see service programs arrive on the
>      '400.
>
>      ____________
>      Paul Cunnane
>      The Learning Company
>
> ______________________________ Reply Separator 
>_________________________________
> Subject: RE: RPG 400 code on the NET
> Author:  Chris Bipes <ChrisB@Cross-check.com> at InterNet
> Date:    17-09-99 9:51 am
>
> As a fairly new programmer to the ILE environment I love the code snippets I
> have received here.  What we need is an EXAMPLE library that can be
> downloaded and searched.  I am not looking for service programs to add to my
> library.  Hell that would be building another Microsoft Windows environment.
> Lots of DLL to use and no way to see if they have bugs.  The same function
> available in a multitude of service programs.
>
> What we need to do is share Ideas.  Say Hey I have coded that before and
> here is how I did it.  We then can modify the source for our own in-house
> coding standards and add to our own in-house libraries.  Forget all
> copyrights and help each other out.  This list has help me to learn lots.
> When I have a completely tested Sockets service program that behaves the way
> I want it to,  I will post on this list.  I welcome all constructive
> comments that I may Get.  Here is a short cut to where I have posted my work
> to date.
>
> HTTP://www.cableone.net/ckb62/socksrv.rpgle
> HTTP://www.cableone.net/ckb62/tcpipsock.rpgle
> HTTP://www.cableone.net/ckb62/tcpipsockp.rpgle
>
>
>
>
> Christopher K. Bipes    mailto:ChrisB@Cross-Check.com
> Sr. Programmer/Analyst  mailto:Chris_Bipes@Yahoo.com
> CrossCheck, Inc.                http://www.cross-check.com
> 6119 State Farm Drive   Phone: 707 586-0551 x 1102
> Rohnert Park CA  94928  Fax: 707 586-1884
>
> *Note to Recruiters
> I nor anyone that I know of is interested in any new and/or exciting
> positions. Please do not contact me.
>
> -----Original Message-----
> From: James W. Kilgore [mailto:qappdsn@ibm.net]
> Sent: Thursday, September 16, 1999 9:41 PM
> To: RPG400-L@midrange.com
> Subject: Re: RPG 400 code on the NET
>
>
> Jim,
>
> Now I'm no lawyer, but I disagree with you about the GPL license in regard
> to code
> snippets.
>
> As I read it, the GPL license prohibits one from profiteering from a
> derivative of
> another's work.  In the original context of the GPL license, the original
> work is a
> "full and working program".  Subsequent contributors would refine the
> original work.
>
> The original author and contributors are all acknowledged.  It's more of an
> informal
> resume building exercise.
>
> For example, I have a routine which allows one to build an available Fxx key
> text
> string on the fly.  As such, it is not a "full and working program" and I
> would not
> place it in public domain under the GPL license.  I -would- put it out for
> public use
> under a shareware license.
>
> The normal practice for shareware would require that copyright be
> acknowledged and
> notice of such retained in all derivative works.
> The nominal request for "registration" fees aid in the support of
> experimental works.
> It is a way of funding a hobby.
>
> AFAIK, the GPL license requires that the source code be made available for
> anyone to
> modify.  A service program under a shareware license would not have such a
> restriction.  There is a "free for personal use" clause, but a caveat about
> commercial
> (for profit) use.  If you want to use the code in a commercial product, you
> must
> contact the author and negotiate a license agreement.
>
> This may be a better suited venue for AS/400 shared code.
>
> Jim Langston wrote:
>
> > I don't' think we want to do that, Paul.  If I use someone's code snippet
> > in a program I write, I want to be able to turn around and sell that
> > program.  Well, right now I'm working for another company, and we
> > are using everything in house, but others may want to sell their programs.
> >
> > I have no objection to giving someone some code, they include it in
> > a program, then make a million dollars off it, more power to them.
> >
> > What I think we are talking about here is making everyone's life
> > a lot easier by making us all reinvent the wheel.
> >
> > The GPL license says that if you use that code in your program, you
> > can not then sell your program.
> >
> > Regards,
> >
> > Jim Langston
> >
>
> +---
> | This is the RPG/400 Mailing List!
> | To submit a new message, send your mail to RPG400-L@midrange.com.
> | To subscribe to this list send email to RPG400-L-SUB@midrange.com.
> | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
> david@midrange.com
> +---
> +---
> | This is the RPG/400 Mailing List!
> | To submit a new message, send your mail to RPG400-L@midrange.com.
> | To subscribe to this list send email to RPG400-L-SUB@midrange.com.
> | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator: david@midrange.com
> +---
> +---
> | This is the RPG/400 Mailing List!
> | To submit a new message, send your mail to RPG400-L@midrange.com.
> | To subscribe to this list send email to RPG400-L-SUB@midrange.com.
> | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator: david@midrange.com
> +---

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---