[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
problem with mlock in current hg
From: |
John W. Eaton |
Subject: |
problem with mlock in current hg |
Date: |
Fri, 06 Jun 2008 11:37:26 -0400 |
On 6-Jun-2008, Shai Ayal wrote:
| using the current dev version, I cannot mlock a function. when I try I
| get the mlock usage text.
|
| Shai
|
|
| octave:1> function f(a); b=a;endfunction;
| octave:2> mlock("f")
|
| Invalid call to mlock. Correct usage is:
|
| -- Built-in Function: mlock (NAME)
Since mlock can only work from within a function, to lock the
currently executing function. So I think this is just a minor bug in
the documentation. I checked in the following change.
jwe
# HG changeset patch
# User John W. Eaton <address@hidden>
# Date 1212766510 14400
# Node ID bff8dbc1be117b8e3d770355c038dd49313ff9a1
# Parent e3a502930e2ab373fd0e923d351fc0abbae243c7
mlock: doc fix
diff --git a/src/ChangeLog b/src/ChangeLog
--- a/src/ChangeLog
+++ b/src/ChangeLog
@@ -1,3 +1,7 @@
+2008-06-06 John W. Eaton <address@hidden>
+
+ * variables.cc (Fmlock): Doc fix.
+
2008-06-05 John W. Eaton <address@hidden>
* gl-render.cc (opengl_renderer::draw): Correctly avoid shadow
diff --git a/src/variables.cc b/src/variables.cc
--- a/src/variables.cc
+++ b/src/variables.cc
@@ -1930,7 +1930,7 @@
DEFCMD (mlock, args, ,
"-*- texinfo -*-\n\
address@hidden {Built-in Function} {} mlock (@var{name})\n\
address@hidden {Built-in Function} {} mlock ()\n\
Lock the current function into memory so that it can't be cleared.\n\
@seealso{munlock, mislocked, persistent}\n\
@end deftypefn")