Path: news.mathworks.com!not-for-mail
From: "Bruno Luong" <b.luong@fogale.findmycountry>
Newsgroups: comp.soft-sys.matlab
Subject: Re: Error from using  dgecon of LAPACK and BLAS in R2009a
Date: Wed, 5 Aug 2009 12:29:02 +0000 (UTC)
Organization: FOGALE nanotech
Lines: 12
Message-ID: <h5btue$rea$1@fred.mathworks.com>
References: <h5bb4h$ee8$1@fred.mathworks.com> <h5bmlv$pb7$1@fred.mathworks.com> <h5bs8j$6pd$1@fred.mathworks.com>
Reply-To: "Bruno Luong" <b.luong@fogale.findmycountry>
NNTP-Posting-Host: webapp-02-blr.mathworks.com
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Trace: fred.mathworks.com 1249475342 28106 172.30.248.37 (5 Aug 2009 12:29:02 GMT)
X-Complaints-To: news@mathworks.com
NNTP-Posting-Date: Wed, 5 Aug 2009 12:29:02 +0000 (UTC)
X-Newsreader: MATLAB Central Newsreader 390839
Xref: news.mathworks.com comp.soft-sys.matlab:560976


"Renwen Lin" <linrenwen@gmail.com> wrote in message <h5bs8j$6pd$1@fred.mathworks.com>...
> Bruno,   Thanks so much,
> 
> After read few introductions of _stdcall.  I think A   __stdcall  is supposed to deal with function's  arguments, and I can not understood why it is needed here. It seems my problem is mex compile can not identify the function rather than its arguments.  
> 
> Hope you can explain it a little more for me.

The calling convention affects how arguments are put on the stack, but also have the function name are decorated and exported.

There is a tool to inspect what are the function names in a library. I can't recall it right now.

Bruno