Re: MacTCP vs OT (was) [MacPerl] calling Perl script from applescript (fwd)

[mark@cheers.jsc.nasa.gov (Mark Manning/Muniz Eng.)]

According to Matthias Ulrich Neeracher:
> [We're starting to stray a bit from MacPerl again]
*nod*

> The performance and interface are good. OT as an implementation looks good
> enough to switch. OT as an API, however, does not have much of a future,
> as far as I know. Rhapsody will presumably have sockets.
So MacPerl doesn't have any problems with OT that you are
aware of.  I just set the thing up last night when I got
home (late).  I'm going to be trying out some programs
(MacPerl ones) tonight.  So I guess I'll see if there is
any kind of a problem with MacPerl and OT.  :-)

Would it be a problem with MacTCP (and not MacPerl) which
caused MacTCP to not connect to my ISP?  The only
difference from before was that I upgraded to OS 7.6 (and
now 7.6.1 last night).  So it is probable that I might have
needed to download the latest and greatest version of
MacTCP/IP rather than anything which MacPerl might have to
do with it.  (ie: This is why the "Do I need to re-install
MacPerl" question from before was asked.)

Ok, if the new OS is going to sockets, how would this
affect MacPerl?  I remember reading that under the new OS
MacPerl might be a thing of the past.  This would (to me)
be a shame.  But if MacPerl is sticking around, would this
entail a major re-write?  Or is it simpler to maintain
because of the new OS being a flavor of Unix?  (Just
wondering and trying to move this more back towards the
MacPerl list.  :-) )

***** Want to unsubscribe from this list?
***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch