Path: news.mathworks.com!not-for-mail
From: "Michael Hosea" <Michael.Hosea@mathworks.com>
Newsgroups: comp.soft-sys.matlab
Subject: Re: Last drop in a user's patience
Date: Sat, 15 Nov 2008 12:59:59 -0500
Organization: The MathWorks, Inc.
Lines: 21
Message-ID: <gfn2mv$5m2$1@fred.mathworks.com>
References: <gflcij$3rm$1@fred.mathworks.com> <gfm2c2$37h$1@fred.mathworks.com>
Reply-To: "Michael Hosea" <Michael.Hosea@mathworks.com>
NNTP-Posting-Host: hoseam.dhcp.mathworks.com
X-Trace: fred.mathworks.com 1226771999 5826 144.212.115.185 (15 Nov 2008 17:59:59 GMT)
X-Complaints-To: news@mathworks.com
NNTP-Posting-Date: Sat, 15 Nov 2008 17:59:59 +0000 (UTC)
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5512
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Xref: news.mathworks.com comp.soft-sys.matlab:501006


MATLAB is not moving in that direction.  Mex files are still supported.  As 
far as I know, capabilities along these lines have only been *increasing*. 
However, now the mex file must be compiled for the right target system. 
E.g., for execution in a 32bit windows environment, it should be .mexw32, 
which is now the default for the mex command when run on a 32bit windows 
platform.
--
Mike

"Mark" <mark.e.eigenraam@dse.vic.gov.au> wrote in message 
news:gfm2c2$37h$1@fred.mathworks.com...
>I am also concerned with the lack of compatability of matlab with dlls, 
>matlab is not known for its speed for simulation so why not let us use 
>matlab for what it is good at, building applications, but leave us to 
>decide if we use fortran or C for our dlls and heavy duty crunching needs. 
>alternatively we go back to the core languages. one needs to know thier 
>limits and matlab is moving into to shaking territory
>
> mark