|
> From: RPower@xxxxxxxxxx > > If I'm debugging, I had better be able to see the source code of the > modules I'm calling. > > As a person creating a program with cutting edge technology, exactly why > would I want you to be able to see the source code? For that matter why > would you want ot be debugging it? That's what customer support is for > isn't it? I don't understand this, Ron. I see two primary development scenarios. First, I'm developing in-house software (or software for sale, doesn't matter) where I'm using an API someone else in the company wrote. In that case, I should always be able to see the source, at least in my mind. The other is when I buy someone else's product and they supply APIs. I suppose in that scenario I don't need to see their code (although historically midrange applications have come with source). Do you disagree in both cases? I guess I can see your point even in scenario one, but I wonder what other people think. Me, I love to see the source. I like stepping through the JVM source to see what it's doing. Joe
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.