From maintainers-request at octave dot org Fri Feb 17 19:06:12 2006
Subject: Re: "oct files" within the embedder
From: "Sebastien Loisel" <sloisel at gmail dot com>
To: "Paul Kienzle" <pkienzle at users dot sourceforge dot net>
Cc: "David Bateman" <david dot bateman at motorola dot com>,         "octave maintainers mailing list" <maintainers@octave.org>
Date: Sat, 18 Feb 2006 02:04:32 +0100

------=_Part_1181_26353919.1140224672911
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

OK, thanks.

I fixed my help system problems. I'm releasing a new version as I write
this.

Sebastien Loisel

On 2/18/06, Paul Kienzle <pkienzle at users dot sourceforge dot net> wrote:
>
> Look at listen.cc.  I register the send and senderror functions:
>
> #if USE_DEFUN_INTERNAL
>    install_builtin_function (Fsend, "send", "builtin send doc", false);
>    install_builtin_function (Fsenderror,
>                              "senderror", "builtin senderror doc",
> false);
> #endif
>
> - Paul
>
> On Feb 17, 2006, at 8:19 AM, Sebastien Loisel wrote:
>
> > David,
> >
> > If I mkoctfile foo.cpp -o foo.oct then I get a function in octave,
> > called foo, that I can call. However, if instead I g++ foo.cpp -o
> > foo.o and then statically link foo.o into my embedder, the function
> > isn't visible in octave. Is there a way for my embedder to add it to
> > the namespace, or am I better off just making oct files?
> >
> > Cheers,
> >
> > S=E9bastien Loisel
>
>
>

------=_Part_1181_26353919.1140224672911
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

OK, thanks.<br>
<br>
I fixed my help system problems. I'm releasing a new version as I write thi=
s.<br>
<br>
Sebastien Loisel<br><br><div><span class=3D"gmail_quote">On 2/18/06, <b cla=
ss=3D"gmail_sendername">Paul Kienzle</b> &lt;<a href=3D"mailto:pkienzle at use=
rs dot sourceforge dot net">pkienzle at users dot sourceforge dot net</a>&gt; wrote:</span><bl=
ockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, 204=
, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Look at listen.cc.&nbsp;&nbsp;I register the send and senderror functions:<=
br><br>#if USE_DEFUN_INTERNAL<br>&nbsp;&nbsp; install_builtin_function (Fse=
nd, &quot;send&quot;, &quot;builtin send doc&quot;, false);<br>&nbsp;&nbsp;=
 install_builtin_function (Fsenderror,
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;
&quot;senderror&quot;, &quot;builtin senderror doc&quot;,<br>false);<br>#en=
dif<br><br>- Paul<br><br>On Feb 17, 2006, at 8:19 AM, Sebastien Loisel wrot=
e:<br><br>&gt; David,<br>&gt;<br>&gt; If I mkoctfile foo.cpp -o foo.oct
 then I get a function in octave,<br>&gt; called foo, that I can call. Howe=
ver, if instead I g++ foo.cpp -o<br>&gt; foo.o and then statically link foo=
.o into my embedder, the function<br>&gt; isn't visible in octave. Is there=
 a way for my embedder to add it to
<br>&gt; the namespace, or am I better off just making oct files?<br>&gt;<b=
r>&gt; Cheers,<br>&gt;<br>&gt; S=E9bastien Loisel<br><br><br></blockquote><=
/div><br>

------=_Part_1181_26353919.1140224672911--