> -----Original Message-----
> From: Mo DeJong [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, August 09, 2000 5:14 PM
> To: [EMAIL PROTECTED]
> Subject: [Tcl Java] Re: TclBlend Initialization Mutex
>
> > Yes, they may be fixed in the future. Though I can't stop
> working waiting
> > for them to be fixed. So I have to work with what I can get today.
>
> Which means getting them working in threaded Tcl, right?
Not always. The goal is to find tools and components that help with the
fast development of products for our customers. Sometimes, we rather
rewrite a piece of functionality from scratch, which makes it proprietary.
We try to use as much off the shelf components as possible. But if the
extension doesn't work off the shelf, then it is very hard to justify using
it at all. We are not a Tcl only environment, if Tcl extensions don't work
well, we start assimilating other technologies. (We are Borg ... :-)
> Binary downloads just don't work. I tired over an over again
> during the 1.2 process. People would complain that they did
> not want to compile, so I put up a binary version. Shock
> and horrors, people could not get that to work either.
> A binary has all sorts of problems, mismatched versions
> of Tcl, the JVM, wrong env settings, and so on.
I certainly have a lot of sympathy for your frustration.
> I think the best approach is to just lock down Tcl Blend
> so that it only builds with a Thread enabled Tcl. People
> are going to need to download an build Tcl and Tcl Blend,
> there is just no way around it. It would be better to
> just work on the "Tcl SDK" idea, a common build environment
> would make things a lot easier.
Let's say we all use "Tcl SDK". I get it and compile my own Tcl. Ship the
binaries to my customers. They complain about things not working. The
problem has not been solved by the SDK.
There is a solution to the binary problem because many commercial companies
do distribute binary programs and libraries. I guess the amount of
resources involved in verifying these binaries is beyond the capability of
one person with just a few pieces of equipment. It is certainly not right
to blame any individual for non-working binary distributions of public
domain software.
Getting everyone to compile Tcl is not the right solution, but I suppose it
is the cheapest solution and takes the heat off the people who already
contributed a lot to the product. Maybe a company can provide binary
distribution service and charge $99 per copy to cover the cost of the
testing, follow the commercial Linux model.
-- Jiang Wu
[EMAIL PROTECTED]
----------------------------------------------------------------
The TclJava mailing list is sponsored by Scriptics Corporation.
To subscribe: send mail to [EMAIL PROTECTED]
with the word SUBSCRIBE as the subject.
To unsubscribe: send mail to [EMAIL PROTECTED]
with the word UNSUBSCRIBE as the subject.
To send to the list, send email to '[EMAIL PROTECTED]'.
An archive is available at http://www.mail-archive.com/tcljava@scriptics.com
