octave-dev — GNU Octave developers' list

[OctDev] [PATCH] CVS-octave-forge and GCC3.2

[Nix <ni...@es...>]

[Apologies for lack of References:, I am not a member of this list.]

octave-forge needs adjustment to handle the new exception-based
interrupt model in the latest CVS octave. I think this fixes it:

2002-11-24  Nix  <ni...@es...>

	* make_sparse.h (SP_FATAL_ERR): Use octave_throw_interrupt_exception()...
	* make_sparse.h (includes): ... declared in quit.h.

Index: octave-forge/main/sparse/make_sparse.h
===================================================================
RCS file: /cvsroot/octave/octave-forge/main/sparse/make_sparse.h,v
retrieving revision 1.9
diff -u -r1.9 make_sparse.h
--- octave-forge/main/sparse/make_sparse.h	5 Nov 2002 19:21:07 -0000	1.9
+++ octave-forge/main/sparse/make_sparse.h	24 Nov 2002 21:40:14 -0000
@@ -89,7 +89,7 @@
 // Thanks to To: Paul Kienzle <pki...@ki...>
 // for help with error handling 
 #define SP_FATAL_ERR(str) { error("sparse: %s", str);  \
-                            jump_to_top_level ();  \
+                            octave_throw_interrupt_exception ();  \
                             panic_impossible (); }
 
 // The SuperLU includes need to be first,
@@ -132,6 +132,7 @@
 #include <octave/ov-complex.h>
 #include <octave/ov-re-mat.h>
 #include <octave/ov-cx-mat.h>
+#include <octave/quit.h>
 #include <octave/pager.h>
 #include <octave/pr-output.h>
 #include <octave/symtab.h>

-- 
`I keep hearing about SF writers dying, but I never hear about SF
 writers being born.  So I guess eventually there'll be none left.'
                                    -- Keith F. Lynch

[OctDev] Adding a Mac OS X section

[Per P. <per...@ma...>]

Hi all!

Thought I'd just introduce myself! Paul added me to the project to take 
care of Mac OS X issues...
So, to save myself from too many questions, I added a short 
INSTALL.MacOSX as well as a extra/MacOSX section.

Cheers,
Per

(Who is thinking of starting his own "switch" campaign:
"I switched from MatLab a year ago and never looked back..." ;-)

------------
Per Persson
Blekinge Institute of Technology
Dept. of Signal Processing and Telecommunications

www:   http://www.its.bth.se/staff/pee
e-mail: per...@bt...

[OctDev] bug in minimize.m?

[Steven G. J. <st...@ab...>]

If you look at minimize.m, it seems to call setfield incorrectly (passing
a string/key as the first argument instead of the structure to
modify).  This causes it to fail, with setfield complaining about an odd
number of arguments.

Cordially,
Steven G. Johnson

[OctDev] Re: CVS -octave-forge and GCC3.2 Wrong error-message...corrected

[Ole J. H. <ole...@ya...>]

On Saturday 16 November 2002 13:38, Ole J. Hagen wrote:
> Hi.
>
> I have updated my whole system, which means that I am using gcc-3.2.
> cvs-version of octave-forge has some problems concerning compilation.
> The CVS-version of Octave is compiled with gcc-3.2.
>
> Any suggestions?
>
> Cheers,
>
> Ole
>
>
The Error message is:
koctfile -DHAVE_OCTAVE_21 -s -v conv2.cc
g++ -c -fPIC -I/usr/include/octave-2.1.39 -I/usr/include/octave-2.1.39/oc=
tave=20
-I/usr/include -mieee-fp -march=3Dpentium4 -mcpu=3Dpentium4 -O3 -pipe=20
-fomit-frame-pointer -DHAVE_OCTAVE_21 conv2.cc -o conv2.o
cc1plus: warning: changing search order for system directory "/usr/includ=
e"
cc1plus: warning:   as it has already been specified as a non-system dire=
ctory
conv2.cc: In function `MArray2<T> conv2(MArray<T>&, MArray<T>&, MArray2<T=
>&,
   int) [with T =3D Complex]':
conv2.cc:271:   instantiated from here
conv2.cc:70: `jump_to_top_level' undeclared (first use this function)
conv2.cc:70: (Each undeclared identifier is reported only once for each
   function it appears in.)
make[2]: *** [conv2.oct] Error 1
make[2]: Leaving directory `/home/olejh/Octave/octave-forge/main/image'
make[1]: *** [image/] Error 2
make[1]: Leaving directory `/home/olejh/Octave/octave-forge/main'
make: *** [main/] Error 2

______________________________________________________
Følg VM i fotball 2002 på http://fifaworldcup.yahoo.com

[OctDev] CVS -octave-forge and GCC3.2

[Ole J. H. <ole...@ya...>]

Hi.

I have updated my whole system, which means that I am using gcc-3.2.=20
cvs-version of octave-forge has some problems concerning compilation.=20
The CVS-version of Octave is compiled with gcc-3.2.

Any suggestions?

Cheers,=20

Ole=20


The error-message is:

g++ -c -fPIC -I/usr/include/octave-2.1.39 -I/usr/include/octave-2.1.39/oc=
tave=20
-I/usr/include -mieee-fp -march=3Dpentium4 -mcpu=3Dpentium4 -O3 -pipe=20
-fomit-frame-pointer -DHAVE_OCTAVE_21 conv2.cc -o conv2.o
cc1plus: warning: changing search order for system directory "/usr/includ=
e"
cc1plus: warning:   as it has already been specified as a non-system dire=
ctory
conv2.cc: In function `MArray2<T> conv2(MArray<T>&, MArray<T>&, MArray2<T=
>&,
   int) [with T =3D Complex]':
conv2.cc:271:   instantiated from here
conv2.cc:70: `jump_to_top_level' undeclared in namespace `std'
conv2.cc: In function `MArray2<T> conv2(MArray<T>&, MArray<T>&, MArray2<T=
>&,
   int) [with T =3D double]':
conv2.cc:277:   instantiated from here
conv2.cc:70: `jump_to_top_level' undeclared in namespace `std'
conv2.cc: In function `MArray2<T> conv2(MArray2<T>&, MArray2<T>&, int) [w=
ith T
   =3D Complex]':
conv2.cc:285:   instantiated from here
conv2.cc:170: `jump_to_top_level' undeclared (first use this function)
conv2.cc:170: (Each undeclared identifier is reported only once for each
   function it appears in.)
make[2]: *** [conv2.oct] Error 1
make[2]: Leaving directory `/home/olejh/Octave/octave-forge/main/image'
make[1]: *** [image/] Error 2
make[1]: Leaving directory `/home/olejh/Octave/octave-forge/main'
make: *** [main/] Error 2

______________________________________________________
Følg VM i fotball 2002 på http://fifaworldcup.yahoo.com

Re: [OctDev] waitbar function

[Paul K. <pki...@ja...>]

I twiddled the build files for waitbar a little so that it will
at least compile on cygwin.  Unfortunately octave core dumps when
I try to run it.

Please try my changes on your configuration.

As Etienne says, do ./autogen.sh; ./configure; from the octave-forge
directory before doing make.

- Paul

On Tue, Nov 12, 2002 at 03:51:03PM +0000, Etienne Grossmann wrote:
> 
>   Hello,
> 
> just to say that I commited Quentin Spencer's waitbar.cc on
> octave-forge, in main/miscellaneous.
> 
>    I also added 
> 
>      main/miscellaneous/(Makeconf.add|configure.add|Makefile)
> 
> so that the header file term.h be searched for when ./configure is
> run. I inspired myself from the files in main/image/ for this purpose.
> 
>   Could people check that all is ok? (don't forget to do ./autogen.sh
> so that ./configure be generated).
> 
>      ./autogen.sh            # Generate ./configure
>      ./configure             # Should give a message about term.h
>      make                    # Should build waitbar.cc
> 
> and then check that, in octave,
> 
>      N=50; for i=0:N ; waitbar (i/N); sleep(2/N); end
> 
> produces a progressing waitbar?
> 
>   Cheers,
> 
>   Etienne
> 
> 
> On Tue, Nov 12, 2002 at 12:59:16AM +0100, Quentin Spencer wrote:
> # Hello,
> # 
> # Here's my fix to the waitbar function. If you can figure out the 
> # configure stuff, go ahead and put it into octave-forge. The problem was 
> # some escape characters that weren't being cleared and it seems xterm 
> # reacts to this differently than the KDE and GNOME terminals.
> # 
> # cheers,
> # Quentin
> # 
> # 
> # 
> # Etienne Grossmann wrote:
> # 
> # > Hello,
> # >
> # >nice function! Nice in a gnome-terminal, at least. In a xterm, when
> # >the value spans [0,1], the displayed %NN starts in the middle and
> # >*moves left* until it reaches the edge. Then, the %NN disappears and
> # >the white bar progresses until it reaches the middle of the line.
> # >
> # > Will try to fix and see about $OF/configure.base and Makeconf.base.
> # >
> # > Cheers,
> # >
> # > Etienne
> # >
> # 
> # 
> 
> # /**************************************************************************
> #  *  Waitbar function -- displays progress of lengthy calculations
> #  *  -------------------------------------------------------------
> #  *  Copyright (c) 2002  Quentin Spencer (qsp...@ie...)
> #  *
> #  *  This library is free software; you can redistribute it and/or
> #  *  modify it under the terms of the GNU Library General Public
> #  *  License as published by the Free Software Foundation; either
> #  *  version 2 of the License, or (at your option) any later version.
> #  *
> #  *  This library is distributed in the hope that it will be useful,
> #  *  but WITHOUT ANY WARRANTY; without even the implied warranty of
> #  *  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
> #  *  Library General Public License for more details.
> #  *
> #  *  You should have received a copy of the GNU Library General Public
> #  *  License along with this library; if not, write to the Free
> #  *  Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA
> #  *  02111-1307 USA
> #  *
> #  *
> #  *************************************************************************/
> # 
> # #include "octave/oct.h"
> # #define HAVE_TERM_H 1
> # #if HAVE_TERM_H
> # #include "term.h"
> # #endif
> # 
> # #define BUF_SIZE	256
> # #define MAX_LEN		240
> # #define DEFAULT_LEN	50
> # #define	BAR_CHAR	'#'
> # 
> # static bool no_terminal=false;
> # 
> # DEFUN_DLD(waitbar, args, nargout,
> # "waitbar(...);\n\
> #  WAITBAR displays a text-based wait bar. This function\n\
> #  is similar to the Matlab waitbar command, but it is\n\
> #  a text, rather than graphical function.\n\n\
> #  A typical usage of WAITBAR in a lengthy computation\n\
> #  (inside a FOR loop, for example) is as follows:\n\n\
> #  for i=1:1000\n\
> #      ## computation\n\
> #      waitbar(i/1000);\n\
> #  end\n\n\
> #  WAITBAR(X), where 0 <= X <= 1, sets the position of the\n\
> #  waitbar to the fractional length X. Values of X exactly equal\n\
> #  to 0 or 1 clear the waitbar.\n\n\
> #  If Octave is running in a smart terminal, the width is\n\
> #  automatically detected. Otherwise, it is initialized to a\n\
> #  default of 50 characters, or it can be set to N characters\n\
> #  with WAITBAR(0,N). If no terminal is detected (such as when\n\
> #  Octave is run in batch mode and output is redirected), no\n\
> #  output is generated.\n\n\
> #  For compatibility with the Matlab version of this function\n\
> #  (which is graphical rather than text-based), additional\n\
> #  arguments are ignored, but there are no guarantees of perfect\n\
> #  compatibility.")
> # {
> #   static char print_buf[BUF_SIZE];
> #   static int n_chars_old;
> #   static int pct_int_old;
> #   static int length;
> # #if HAVE_TERM_H
> #   static char term_buffer[1024];
> #   static char *begin_rv, *end_rv;
> #   static int brvlen, ervlen;
> #   static bool smart_term;
> #   int j;
> # #endif
> #   static char *term;
> #   static bool init;
> # 
> #   Matrix arg;
> #   float pct;
> #   int i;
> # 
> #   octave_value_list retval;
> #   int nargin = args.length();
> #   if (nargin < 1) {
> #     print_usage("waitbar");
> #     return retval;
> #   }
> # 
> #   if(no_terminal)
> #     return retval;
> # 
> #   arg	= args(0).matrix_value();
> #   pct	= arg(0,0);
> #   if(pct>1.0)	pct	= 1.0;		// to prevent overflow
> # 
> #   if(pct==0.0 || pct==1.0)
> #     {
> #       init = true;
> #       term = getenv("TERM");
> #       if(!term)
> # 	{
> # 	  no_terminal	= true;
> # 	  return retval;
> # 	}
> # #if HAVE_TERM_H
> #       i = tgetnum("co");
> #       smart_term = i ? true : false;
> # #endif
> #       if(nargin==1)
> # #if HAVE_TERM_H
> # 	length = smart_term ? i-1 : DEFAULT_LEN;
> # #else
> #         length = DEFAULT_LEN;
> # #endif
> #       else
> # 	{
> # 	  length	= args(1).int_value();
> # 	  if(length>MAX_LEN)	length	= MAX_LEN;
> # 	  if(length<=0)		length	= DEFAULT_LEN;
> # 	}
> # #if HAVE_TERM_H
> #       if(smart_term)
> # 	{
> # 	  // get terminal strings ("rv"="reverse video")
> # 	  char* buf_ptr	= term_buffer;
> # 	  begin_rv	= tgetstr("so", &buf_ptr);
> # 	  end_rv	= tgetstr("se", &buf_ptr);
> # 	  brvlen = 0;	buf_ptr = begin_rv;
> # 	  while(buf_ptr[++brvlen]);
> # 	  ervlen = 0;	buf_ptr = end_rv;
> # 	  while(buf_ptr[++ervlen]);
> # 	  
> # 	  // initialize print buffer
> # 	  for(i=0; i<BUF_SIZE; ++i)
> # 	    print_buf[i]		= ' ';
> # 	  print_buf[length+brvlen+ervlen+1] = '\r';
> # 	  print_buf[length+brvlen+ervlen+2] = '\0';
> # 	  for(i=0; i<brvlen; ++i)
> # 	    print_buf[i]	= begin_rv[i];
> # 	  for(i=0; i<ervlen; ++i)
> # 	    print_buf[i+brvlen]	= end_rv[i];
> # 	  printf(print_buf);
> # 	}
> #       else
> # 	{
> # #endif
> # 	  for(i=0; i<BUF_SIZE; ++i)
> # 	    print_buf[i]		= ' ';
> # 	  print_buf[length+8]	= '\r';
> # 	  print_buf[length+9]	= '\0';
> # 	  printf(print_buf);
> # 	  print_buf[0]		= '[';
> # 	  print_buf[length+1]	= ']';
> # #if HAVE_TERM_H
> # 	}
> # #endif
> #       n_chars_old	= 0;
> #       fflush(stdout);
> #       return retval;
> #     }
> #   else
> #     {
> #       // calculate position
> #       int n_chars=(int)(pct*length+0.5);
> #       int pct_int=(int)(pct*100.0+0.5);
> # 
> #       // check to see if we got this far without initialization
> #       if(init==false)
> # 	{
> # 	  Fwaitbar(0.0,0);
> # 	  printf(print_buf);
> # 	  fflush(stdout);
> # 	}
> # 
> #       // check to see of output needs to be updated
> #       if(n_chars!=n_chars_old || pct_int!=pct_int_old)
> # 	{
> # #if HAVE_TERM_H
> # 	  if(smart_term)
> # 	    {
> # 	      static char pct_str[6];
> # 	      int half = length/2-1;
> # 	      sprintf(pct_str,"%3i%%%%",pct_int);
> # 
> # 	      // Clear old percentage string
> # 	      for(i=half, j=0; j<5; ++i, ++j)
> # 		if(i>=n_chars_old)
> # 		  print_buf[i+brvlen+ervlen]	= ' ';
> # 		else
> # 		  print_buf[i+brvlen]	= ' ';
> # 
> # 	      // Clear old and insert new end of reverse video
> # 	      for(i=n_chars_old+brvlen; i<n_chars_old+brvlen+ervlen; ++i)
> # 		print_buf[i]	= ' ';
> # 	      for(i=n_chars+brvlen, j=0; j<ervlen; ++i, ++j)
> # 		print_buf[i]	= end_rv[j];
> # 
> # 	      // Insert the percentage string
> # 	      for(i=half, j=0; j<5; ++i, ++j)
> # 		if(i>=n_chars)
> # 		  print_buf[i+brvlen+ervlen]	= pct_str[j];
> # 		else
> # 		  print_buf[i+brvlen]	= pct_str[j];
> # 	    }
> # 	  else
> # 	    {
> # #endif
> # 	      if(n_chars>=n_chars_old)
> # 		for(int i=n_chars_old+1; i<=n_chars; ++i)
> # 		  print_buf[i]	= BAR_CHAR;
> # 	      else
> # 		for(int i=n_chars+1; i<=n_chars_old; ++i)
> # 		  print_buf[i]	= ' ';
> # 	      sprintf(&(print_buf[length+3])," %3i%%\r",pct_int);
> # #if HAVE_TERM_H
> # 	    }
> # #endif
> # 	  printf(print_buf);
> # 	  fflush(stdout);
> # 	  n_chars_old	= n_chars;
> # 	  pct_int_old	= pct_int;
> # 	}
> #     }
> #   return retval;
> # }
> 
> 
> -- 
> Etienne Grossmann ------ http://www.isr.ist.utl.pt/~etienne
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by: 
> To learn the basics of securing your web site with SSL, 
> click here to get a FREE TRIAL of a Thawte Server Certificate: 
> http://www.gothawte.com/rd522.html
> _______________________________________________
> Octave-dev mailing list
> Oct...@li...
> https://lists.sourceforge.net/lists/listinfo/octave-dev

Re: [OctDev] waitbar function

[Etienne G. <et...@is...>]

  Hello,

just to say that I commited Quentin Spencer's waitbar.cc on
octave-forge, in main/miscellaneous.

   I also added 

     main/miscellaneous/(Makeconf.add|configure.add|Makefile)

so that the header file term.h be searched for when ./configure is
run. I inspired myself from the files in main/image/ for this purpose.

  Could people check that all is ok? (don't forget to do ./autogen.sh
so that ./configure be generated).

     ./autogen.sh            # Generate ./configure
     ./configure             # Should give a message about term.h
     make                    # Should build waitbar.cc

and then check that, in octave,

     N=50; for i=0:N ; waitbar (i/N); sleep(2/N); end

produces a progressing waitbar?

  Cheers,

  Etienne


On Tue, Nov 12, 2002 at 12:59:16AM +0100, Quentin Spencer wrote:
# Hello,
# 
# Here's my fix to the waitbar function. If you can figure out the 
# configure stuff, go ahead and put it into octave-forge. The problem was 
# some escape characters that weren't being cleared and it seems xterm 
# reacts to this differently than the KDE and GNOME terminals.
# 
# cheers,
# Quentin
# 
# 
# 
# Etienne Grossmann wrote:
# 
# > Hello,
# >
# >nice function! Nice in a gnome-terminal, at least. In a xterm, when
# >the value spans [0,1], the displayed %NN starts in the middle and
# >*moves left* until it reaches the edge. Then, the %NN disappears and
# >the white bar progresses until it reaches the middle of the line.
# >
# > Will try to fix and see about $OF/configure.base and Makeconf.base.
# >
# > Cheers,
# >
# > Etienne
# >
# 
# 

# /**************************************************************************
#  *  Waitbar function -- displays progress of lengthy calculations
#  *  -------------------------------------------------------------
#  *  Copyright (c) 2002  Quentin Spencer (qsp...@ie...)
#  *
#  *  This library is free software; you can redistribute it and/or
#  *  modify it under the terms of the GNU Library General Public
#  *  License as published by the Free Software Foundation; either
#  *  version 2 of the License, or (at your option) any later version.
#  *
#  *  This library is distributed in the hope that it will be useful,
#  *  but WITHOUT ANY WARRANTY; without even the implied warranty of
#  *  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
#  *  Library General Public License for more details.
#  *
#  *  You should have received a copy of the GNU Library General Public
#  *  License along with this library; if not, write to the Free
#  *  Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA
#  *  02111-1307 USA
#  *
#  *
#  *************************************************************************/
# 
# #include "octave/oct.h"
# #define HAVE_TERM_H 1
# #if HAVE_TERM_H
# #include "term.h"
# #endif
# 
# #define BUF_SIZE	256
# #define MAX_LEN		240
# #define DEFAULT_LEN	50
# #define	BAR_CHAR	'#'
# 
# static bool no_terminal=false;
# 
# DEFUN_DLD(waitbar, args, nargout,
# "waitbar(...);\n\
#  WAITBAR displays a text-based wait bar. This function\n\
#  is similar to the Matlab waitbar command, but it is\n\
#  a text, rather than graphical function.\n\n\
#  A typical usage of WAITBAR in a lengthy computation\n\
#  (inside a FOR loop, for example) is as follows:\n\n\
#  for i=1:1000\n\
#      ## computation\n\
#      waitbar(i/1000);\n\
#  end\n\n\
#  WAITBAR(X), where 0 <= X <= 1, sets the position of the\n\
#  waitbar to the fractional length X. Values of X exactly equal\n\
#  to 0 or 1 clear the waitbar.\n\n\
#  If Octave is running in a smart terminal, the width is\n\
#  automatically detected. Otherwise, it is initialized to a\n\
#  default of 50 characters, or it can be set to N characters\n\
#  with WAITBAR(0,N). If no terminal is detected (such as when\n\
#  Octave is run in batch mode and output is redirected), no\n\
#  output is generated.\n\n\
#  For compatibility with the Matlab version of this function\n\
#  (which is graphical rather than text-based), additional\n\
#  arguments are ignored, but there are no guarantees of perfect\n\
#  compatibility.")
# {
#   static char print_buf[BUF_SIZE];
#   static int n_chars_old;
#   static int pct_int_old;
#   static int length;
# #if HAVE_TERM_H
#   static char term_buffer[1024];
#   static char *begin_rv, *end_rv;
#   static int brvlen, ervlen;
#   static bool smart_term;
#   int j;
# #endif
#   static char *term;
#   static bool init;
# 
#   Matrix arg;
#   float pct;
#   int i;
# 
#   octave_value_list retval;
#   int nargin = args.length();
#   if (nargin < 1) {
#     print_usage("waitbar");
#     return retval;
#   }
# 
#   if(no_terminal)
#     return retval;
# 
#   arg	= args(0).matrix_value();
#   pct	= arg(0,0);
#   if(pct>1.0)	pct	= 1.0;		// to prevent overflow
# 
#   if(pct==0.0 || pct==1.0)
#     {
#       init = true;
#       term = getenv("TERM");
#       if(!term)
# 	{
# 	  no_terminal	= true;
# 	  return retval;
# 	}
# #if HAVE_TERM_H
#       i = tgetnum("co");
#       smart_term = i ? true : false;
# #endif
#       if(nargin==1)
# #if HAVE_TERM_H
# 	length = smart_term ? i-1 : DEFAULT_LEN;
# #else
#         length = DEFAULT_LEN;
# #endif
#       else
# 	{
# 	  length	= args(1).int_value();
# 	  if(length>MAX_LEN)	length	= MAX_LEN;
# 	  if(length<=0)		length	= DEFAULT_LEN;
# 	}
# #if HAVE_TERM_H
#       if(smart_term)
# 	{
# 	  // get terminal strings ("rv"="reverse video")
# 	  char* buf_ptr	= term_buffer;
# 	  begin_rv	= tgetstr("so", &buf_ptr);
# 	  end_rv	= tgetstr("se", &buf_ptr);
# 	  brvlen = 0;	buf_ptr = begin_rv;
# 	  while(buf_ptr[++brvlen]);
# 	  ervlen = 0;	buf_ptr = end_rv;
# 	  while(buf_ptr[++ervlen]);
# 	  
# 	  // initialize print buffer
# 	  for(i=0; i<BUF_SIZE; ++i)
# 	    print_buf[i]		= ' ';
# 	  print_buf[length+brvlen+ervlen+1] = '\r';
# 	  print_buf[length+brvlen+ervlen+2] = '\0';
# 	  for(i=0; i<brvlen; ++i)
# 	    print_buf[i]	= begin_rv[i];
# 	  for(i=0; i<ervlen; ++i)
# 	    print_buf[i+brvlen]	= end_rv[i];
# 	  printf(print_buf);
# 	}
#       else
# 	{
# #endif
# 	  for(i=0; i<BUF_SIZE; ++i)
# 	    print_buf[i]		= ' ';
# 	  print_buf[length+8]	= '\r';
# 	  print_buf[length+9]	= '\0';
# 	  printf(print_buf);
# 	  print_buf[0]		= '[';
# 	  print_buf[length+1]	= ']';
# #if HAVE_TERM_H
# 	}
# #endif
#       n_chars_old	= 0;
#       fflush(stdout);
#       return retval;
#     }
#   else
#     {
#       // calculate position
#       int n_chars=(int)(pct*length+0.5);
#       int pct_int=(int)(pct*100.0+0.5);
# 
#       // check to see if we got this far without initialization
#       if(init==false)
# 	{
# 	  Fwaitbar(0.0,0);
# 	  printf(print_buf);
# 	  fflush(stdout);
# 	}
# 
#       // check to see of output needs to be updated
#       if(n_chars!=n_chars_old || pct_int!=pct_int_old)
# 	{
# #if HAVE_TERM_H
# 	  if(smart_term)
# 	    {
# 	      static char pct_str[6];
# 	      int half = length/2-1;
# 	      sprintf(pct_str,"%3i%%%%",pct_int);
# 
# 	      // Clear old percentage string
# 	      for(i=half, j=0; j<5; ++i, ++j)
# 		if(i>=n_chars_old)
# 		  print_buf[i+brvlen+ervlen]	= ' ';
# 		else
# 		  print_buf[i+brvlen]	= ' ';
# 
# 	      // Clear old and insert new end of reverse video
# 	      for(i=n_chars_old+brvlen; i<n_chars_old+brvlen+ervlen; ++i)
# 		print_buf[i]	= ' ';
# 	      for(i=n_chars+brvlen, j=0; j<ervlen; ++i, ++j)
# 		print_buf[i]	= end_rv[j];
# 
# 	      // Insert the percentage string
# 	      for(i=half, j=0; j<5; ++i, ++j)
# 		if(i>=n_chars)
# 		  print_buf[i+brvlen+ervlen]	= pct_str[j];
# 		else
# 		  print_buf[i+brvlen]	= pct_str[j];
# 	    }
# 	  else
# 	    {
# #endif
# 	      if(n_chars>=n_chars_old)
# 		for(int i=n_chars_old+1; i<=n_chars; ++i)
# 		  print_buf[i]	= BAR_CHAR;
# 	      else
# 		for(int i=n_chars+1; i<=n_chars_old; ++i)
# 		  print_buf[i]	= ' ';
# 	      sprintf(&(print_buf[length+3])," %3i%%\r",pct_int);
# #if HAVE_TERM_H
# 	    }
# #endif
# 	  printf(print_buf);
# 	  fflush(stdout);
# 	  n_chars_old	= n_chars;
# 	  pct_int_old	= pct_int;
# 	}
#     }
#   return retval;
# }


-- 
Etienne Grossmann ------ http://www.isr.ist.utl.pt/~etienne

Re: [OctDev] waitbar function

[Quentin S. <qsp...@ie...>]

Hello,

Here's my fix to the waitbar function. If you can figure out the 
configure stuff, go ahead and put it into octave-forge. The problem was 
some escape characters that weren't being cleared and it seems xterm 
reacts to this differently than the KDE and GNOME terminals.

cheers,
Quentin



Etienne Grossmann wrote:

>  Hello,
>
>nice function! Nice in a gnome-terminal, at least. In a xterm, when
>the value spans [0,1], the displayed %NN starts in the middle and
>*moves left* until it reaches the edge. Then, the %NN disappears and
>the white bar progresses until it reaches the middle of the line.
>
>  Will try to fix and see about $OF/configure.base and Makeconf.base.
>
>  Cheers,
>
>  Etienne
>

Re: [OctDev] "Da Coda Al Fine" Document

[Paul K. <pki...@ja...>]

Sure, send it my way.

Paul Kienzle
pki...@us...

On Thu, Nov 07, 2002 at 06:09:14PM +0100, Quentin Spencer wrote:
> I recall someone recently on one of these lists looking for that "Da 
> Coda Al Fine" document from the now-defunct hammersmith-consulting.com. 
> I just found a copy of it in some of my old archives. If the maintainer 
> (whichever one of you it is) is interested in putting this link back on 
> the main octave.sf.net page, contact me and I'll send you the file.
> 
> Quentin Spencer
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by: See the NEW Palm 
> Tungsten T handheld. Power & Color in a compact size!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
> _______________________________________________
> Octave-dev mailing list
> Oct...@li...
> https://lists.sourceforge.net/lists/listinfo/octave-dev

[OctDev] "Da Coda Al Fine" Document

[Quentin S. <qsp...@ie...>]

I recall someone recently on one of these lists looking for that "Da 
Coda Al Fine" document from the now-defunct hammersmith-consulting.com. 
I just found a copy of it in some of my old archives. If the maintainer 
(whichever one of you it is) is interested in putting this link back on 
the main octave.sf.net page, contact me and I'll send you the file.

Quentin Spencer

Re: [OctDev] waitbar function

[Etienne G. <et...@is...>]

  Hello,

nice function! Nice in a gnome-terminal, at least. In a xterm, when
the value spans [0,1], the displayed %NN starts in the middle and
*moves left* until it reaches the edge. Then, the %NN disappears and
the white bar progresses until it reaches the middle of the line.

  Will try to fix and see about $OF/configure.base and Makeconf.base.

  Cheers,

  Etienne

On Thu, Nov 07, 2002 at 01:58:40AM +0100, Quentin Spencer wrote:
# Dear octave community,
# 
# Attached is a waitbar function that I discussed in a earlier mail a few
# weeks ago. It approximates the Matlab command by the same name, but uses
# terminal functions rather than graphics, and attempts to use compatible
# syntax as much as possible. It has code for compilation both with and
# without the "term.h" system header by looking for the HAVE_TERM_H flag.
# I have not figured out how to generate the associated config.in files,
# as my knowledge of these tools is minimal. If someone is willing to do
# this, or can explain in a short e-mail how this is done, please do so.
# 
# Also a second, unrelated question. Since upgrading my RedHat system to
# version 8.0 with GCC 3.2, and updating octave to 2.1.39, octave-forge
# does not compile. Is this a known problem?

  I think Paul mentioned this, but I did not look into it.

# thanks,
# Quentin Spencer
# 
# 

# /**************************************************************************
#  *  Waitbar function -- displays progress of lengthy calculations
#  *  -------------------------------------------------------------
#  *  Copyright (c) 2002  Quentin Spencer (qsp...@ie...)
#  *
#  *  This library is free software; you can redistribute it and/or
#  *  modify it under the terms of the GNU Library General Public
#  *  License as published by the Free Software Foundation; either
#  *  version 2 of the License, or (at your option) any later version.
#  *
#  *  This library is distributed in the hope that it will be useful,
#  *  but WITHOUT ANY WARRANTY; without even the implied warranty of
#  *  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
#  *  Library General Public License for more details.
#  *
#  *  You should have received a copy of the GNU Library General Public
#  *  License along with this library; if not, write to the Free
#  *  Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA
#  *  02111-1307 USA
#  *
#  *
#  *************************************************************************/
# 
# #include "octave/oct.h"
# #if HAVE_TERM_H
# #include "term.h"
# #endif
# 
# #define BUF_SIZE	256
# #define MAX_LEN		240
# #define DEFAULT_LEN	50
# #define	BAR_CHAR	'#'
# 
# DEFUN_DLD(waitbar, args, nargout,
# "waitbar(...);\n\
#  WAITBAR displays a text-based wait bar. This function\n\
#  is similar to the Matlab waitbar command, but it is\n\
#  a text, rather than graphical function.\n\n\
#  A typical usage of WAITBAR in a lengthy computation\n\
#  (inside a FOR loop, for example) is as follows:\n\n\
#  for i=1:1000\n\
#      ## computation\n\
#      waitbar(i/1000);\n\
#  end\n\n\
#  WAITBAR(X), where 0 <= X <= 1, sets the position of the\n\
#  waitbar to the fractional length X. Values of X exactly equal\n\
#  to 0 or 1 clear the waitbar.\n\n\
#  If Octave is running in a smart terminal, the width is\n\
#  automatically detected. Otherwise, it is initialized to a\n\
#  default of 50 characters, or it can be set to N characters\n\
#  with WAITBAR(0,N). If no terminal is detected (such as when\n\
#  Octave is run in batch mode and output is redirected), no\n\
#  output is generated.\n\n\
#  For compatibility with the Matlab version of this function\n\
#  (which is graphical rather than text-based), additional\n\
#  arguments are ignored, but there are no guarantees of perfect\n\
#  compatibility.")
# {
#   static char print_buf[BUF_SIZE];
#   static int n_chars_old;
#   static int pct_int_old;
#   static int length;
# #if HAVE_TERM_H
#   static char term_buffer[1024];
#   static char *begin_rv, *end_rv;
#   static int brvlen, ervlen;
#   static bool smart_term;
#   int j;
# #endif
#   static char *term;
#   static bool init;
# 
#   Matrix arg;
#   float pct;
#   int i;
# 
#   octave_value_list retval;
#   int nargin = args.length();
#   if (nargin < 1) {
#     print_usage("waitbar");
#     return retval;
#   }
# 
#   if(no_terminal)
#     return retval;
# 
#   arg	= args(0).matrix_value();
#   pct	= arg(0,0);
#   if(pct>1.0)	pct	= 1.0;		// to prevent overflow
# 
#   if(pct==0.0 || pct==1.0)
#     {
#       init = true;
#       term = getenv("TERM");
#       if(!term)
# 	{
# 	  no_terminal	= true;
# 	  return retval;
# 	}
# #if HAVE_TERM_H
#       i = tgetnum("co");
#       smart_term = i ? true : false;
# #endif
#       if(nargin==1)
# #if HAVE_TERM_H
# 	length = smart_term ? i-1 : DEFAULT_LEN;
# #else
#         length = DEFAULT_LEN;
# #endif
#       else
# 	{
# 	  length	= args(1).int_value();
# 	  if(length>MAX_LEN)	length	= MAX_LEN;
# 	  if(length<=0)		length	= DEFAULT_LEN;
# 	}
# #if HAVE_TERM_H
#       if(smart_term)
# 	{
# 	  // get terminal strings
# 	  char* buf_ptr	= term_buffer;
# 	  begin_rv	= tgetstr("so", &buf_ptr);
# 	  end_rv	= tgetstr("se", &buf_ptr);
# 	  brvlen = 0;	buf_ptr = begin_rv;
# 	  while(buf_ptr[brvlen])	brvlen++;
# 	  ervlen = 0;	buf_ptr = end_rv;
# 	  while(buf_ptr[ervlen])	ervlen++;
# 
# 	  // initialize print buffer
# 	  for(i=0; i<BUF_SIZE; ++i)
# 	    print_buf[i]		= ' ';
# 	  print_buf[length+brvlen+ervlen+1] = '\r';
# 	  print_buf[length+brvlen+ervlen+2] = '\0';
# 	  for(i=0; i<brvlen; ++i)
# 	    print_buf[i]		= begin_rv[i];
# 	  for(i=0; i<ervlen; ++i)
# 	    print_buf[i+brvlen]	= end_rv[i];
# 	  printf(print_buf);
# 	}
#       else
# 	{
# #endif
# 	  for(i=0; i<BUF_SIZE; ++i)
# 	    print_buf[i]		= ' ';
# 	  print_buf[length+8]	= '\r';
# 	  print_buf[length+9]	= '\0';
# 	  printf(print_buf);
# 	  print_buf[0]		= '[';
# 	  print_buf[length+1]	= ']';
# #if HAVE_TERM_H
# 	}
# #endif
#       n_chars_old	= 0;
#       fflush(stdout);
#       return retval;
#     }
#   else
#     {
#       // calculate position
#       int n_chars=(int)(pct*length+0.5);
#       int pct_int=(int)(pct*100.0+0.5);
# 
#       // check to see if we got this far without initialization
#       if(init==false)
# 	{
# 	  Fwaitbar(0.0,0);
# 	  printf(print_buf);
# 	  fflush(stdout);
# 	}
# 
#       // check to see of output needs to be updated
#       if(n_chars!=n_chars_old || pct_int!=pct_int_old)
# 	{
# #if HAVE_TERM_H
# 	  if(smart_term)
# 	    {
# 	      static char pct_str[6];
# 	      int half = length/2-1;
# 	      sprintf(pct_str,"%3i%%%%",pct_int);
# 
# 	      // Clear old percentage string
# 	      for(i=half, j=0; j<5; ++i, ++j)
# 		if(i>n_chars_old)
# 		  print_buf[i+brvlen+ervlen]	= ' ';
# 		else
# 		  print_buf[i+brvlen]	= ' ';
# 
# 	      // Clear old and insert new end of bold stuff
# 	      for(i=n_chars_old+brvlen+1; i<n_chars_old+brvlen+ervlen+1; ++i)
# 		print_buf[i]	= ' ';
# 	      for(i=n_chars+brvlen+1, j=0; i<n_chars+brvlen+ervlen+1; ++i, ++j)
# 		print_buf[i]	= end_rv[j];
# 
# 	      // Insert the percentage string
# 	      for(i=half, j=0; j<5; ++i, ++j)
# 		if(i>n_chars)
# 		  print_buf[i+brvlen+ervlen]	= pct_str[j];
# 		else
# 		  print_buf[i+brvlen]	= pct_str[j];
# 	    }
# 	  else
# 	    {
# #endif
# 	      if(n_chars>=n_chars_old)
# 		for(int i=n_chars_old+1; i<=n_chars; ++i)
# 		  print_buf[i]	= BAR_CHAR;
# 	      else
# 		for(int i=n_chars+1; i<=n_chars_old; ++i)
# 		  print_buf[i]	= ' ';
# 	      sprintf(&(print_buf[length+3])," %3i%%\r",pct_int);
# #if HAVE_TERM_H
# 	    }
# #endif
# 	  printf(print_buf);
# 	  fflush(stdout);
# 	  n_chars_old	= n_chars;
# 	  pct_int_old	= pct_int;
# 	}
#     }
#   return retval;
# }
# 


-- 
Etienne Grossmann ------ http://www.isr.ist.utl.pt/~etienne

[OctDev] waitbar function

[Quentin S. <qsp...@ie...>]

Dear octave community,

Attached is a waitbar function that I discussed in a earlier mail a few
weeks ago. It approximates the Matlab command by the same name, but uses
terminal functions rather than graphics, and attempts to use compatible
syntax as much as possible. It has code for compilation both with and
without the "term.h" system header by looking for the HAVE_TERM_H flag.
I have not figured out how to generate the associated config.in files,
as my knowledge of these tools is minimal. If someone is willing to do
this, or can explain in a short e-mail how this is done, please do so.

Also a second, unrelated question. Since upgrading my RedHat system to
version 8.0 with GCC 3.2, and updating octave to 2.1.39, octave-forge
does not compile. Is this a known problem?

thanks,
Quentin Spencer

[OctDev] sparse problems

[Paul K. <pki...@ja...>]

Just noting that we have yet another problem in octave-forge for
octave post 2.1.36:

[pkienzle@d121245 sparse]$ octave -qf sp_test.m
error: can't perform indexing operations for sparse type
error: evaluating assignment expression near line 559, column 6
error: evaluating for command near line 30, column 1

Yet another thing to fix prior to this month's release.

- Paul

Re: [OctDev] emacs macro for 2.1.39 adaptation

[Paul K. <pki...@ja...>]

I'm a heavy user of

	cvs diff -c *.m

- Paul

On Sun, Nov 03, 2002 at 11:57:15AM +0000, Etienne Grossmann wrote:
> 
>   Hello,
> 
> the intent was to facilitate the transition and make clear what was
> changed and what is new. If bugs appear, one can check that the new
> and old code really do the same. I was tagging lots of code by hand
> and I found the macro useful.
> 
>   Cheers,
> 
>   Etienne
> 
> On Sat, Nov 02, 2002 at 05:53:22PM -0500, Paul Kienzle wrote:
> # Supporting both styles of args will lead to a lot crufty code.  Along with
> # the rapid developments of the past few months (cell array support and 
> # keyed list support) we are going to be doing a lot of things differently.
> # 
> # Do we really want to support pre-2.1.38 Octave?
> # 
> # I've already converted functions in general, image and signal, but I can
> # put backward compatibility support in again if someone wants to take the
> # time to write the preprocessor.
> # 
> # Please use apps available to configure: cc, grep, awk, sed but no perl,
> # python or tcl.
> # 
> # To support the TSA toolbox, the preprocessor should also be able to test
> # for matlab versions.
> # 
> # How about:
> # 
> # 	%function foo (...)      %# pre o2.1.37
> # 	function foo (varargin)  %# post o2.1.37 or post m5.0.0
> # 	%function foo (a1,a2,a3,a4,a5) %# pre m5
> # 
> # Or if you don't want to bother with Matlab 4 support
> # 
> # 	%function foo (...)      %# pre o2.1.37
> # 	function foo (varargin)  %# post o2.1.37 or post m0
> # 
> # We don't have to write the preprocessor now, but it would be nice to
> # nail the syntax.  
> # 
> # Call it with 
> # 	mprep o$OCTAVE_VERSION *.m
> # or
> # 	mprep m$MATLAB_VERSION *.m
> # 
> # 
> # So version is nameMajor.Minor.Patch, and we need pre, post, and, or
> # 
> # We could let name be the null string for octave.
> # 
> # Thoughts?
> # 
> # - Paul
> # 
> # On Sat, Nov 02, 2002 at 01:35:29PM +0000, Etienne Grossmann wrote:
> # > 
> # >   Hello,
> # > 
> # > for those who use emacs and are updating octave code for 2.1.39, the
> # > following macro may come handy to substitute a line like 
> # > 
> # >      function foo (...)
> # > 
> # >   into 
> # > 
> # >      ## pre 2.1.39 function foo (...)
> # >      function foo (...) ## pos 2.1.39
> # > 
> # > , so that it be easy to keep track of the changes.
> # > 
> # >   Hth,
> # > 
> # >   Etienne
> # > 
> # > ======================================================================
> # > ;; Keyboard Macro Editor.  Press C-c C-c to finish; press C-x k RET to cancel.
> # > ;; Original keys: C-a C-k C-y C-a ## S-SPC pre SPC 2.1.39 SPC C-e RET C-y C-e SPC ## SPC pos SPC 2.1.39
> # > 
> # > Command: octadapt
> # > Key: none
> # > 
> # > Macro:
> # > 
> # > C-a			;; beginning-of-line
> # > C-k			;; kill-line
> # > C-y			;; hilit-yank
> # > C-a			;; beginning-of-line
> # > ##			;; self-insert-command * 2
> # > S-SPC
> # > pre			;; self-insert-command * 3
> # > SPC			;; self-insert-command
> # > 2.1.39			;; self-insert-command * 6
> # > SPC			;; self-insert-command
> # > C-e			;; end-of-line
> # > RET			;; newline
> # > C-y			;; hilit-yank
> # > C-e			;; end-of-line
> # > SPC			;; self-insert-command
> # > ##			;; self-insert-command * 2
> # > SPC			;; self-insert-command
> # > pos			;; self-insert-command * 3
> # > SPC			;; self-insert-command
> # > 2.1.39			;; self-insert-command * 6
> # > 
> # > 
> # > -- 
> # > Etienne Grossmann ------ http://www.isr.ist.utl.pt/~etienne
> # > 
> # > 
> # > -------------------------------------------------------
> # > This sf.net email is sponsored by: See the NEW Palm 
> # > Tungsten T handheld. Power & Color in a compact size!
> # > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
> # > _______________________________________________
> # > Octave-dev mailing list
> # > Oct...@li...
> # > https://lists.sourceforge.net/lists/listinfo/octave-dev
> # 
> # 
> 
> -- 
> Etienne Grossmann ------ http://www.isr.ist.utl.pt/~etienne

Re: [OctDev] emacs macro for 2.1.39 adaptation

[Etienne G. <et...@is...>]

  Hello,

the intent was to facilitate the transition and make clear what was
changed and what is new. If bugs appear, one can check that the new
and old code really do the same. I was tagging lots of code by hand
and I found the macro useful.

  Cheers,

  Etienne

On Sat, Nov 02, 2002 at 05:53:22PM -0500, Paul Kienzle wrote:
# Supporting both styles of args will lead to a lot crufty code.  Along with
# the rapid developments of the past few months (cell array support and 
# keyed list support) we are going to be doing a lot of things differently.
# 
# Do we really want to support pre-2.1.38 Octave?
# 
# I've already converted functions in general, image and signal, but I can
# put backward compatibility support in again if someone wants to take the
# time to write the preprocessor.
# 
# Please use apps available to configure: cc, grep, awk, sed but no perl,
# python or tcl.
# 
# To support the TSA toolbox, the preprocessor should also be able to test
# for matlab versions.
# 
# How about:
# 
# 	%function foo (...)      %# pre o2.1.37
# 	function foo (varargin)  %# post o2.1.37 or post m5.0.0
# 	%function foo (a1,a2,a3,a4,a5) %# pre m5
# 
# Or if you don't want to bother with Matlab 4 support
# 
# 	%function foo (...)      %# pre o2.1.37
# 	function foo (varargin)  %# post o2.1.37 or post m0
# 
# We don't have to write the preprocessor now, but it would be nice to
# nail the syntax.  
# 
# Call it with 
# 	mprep o$OCTAVE_VERSION *.m
# or
# 	mprep m$MATLAB_VERSION *.m
# 
# 
# So version is nameMajor.Minor.Patch, and we need pre, post, and, or
# 
# We could let name be the null string for octave.
# 
# Thoughts?
# 
# - Paul
# 
# On Sat, Nov 02, 2002 at 01:35:29PM +0000, Etienne Grossmann wrote:
# > 
# >   Hello,
# > 
# > for those who use emacs and are updating octave code for 2.1.39, the
# > following macro may come handy to substitute a line like 
# > 
# >      function foo (...)
# > 
# >   into 
# > 
# >      ## pre 2.1.39 function foo (...)
# >      function foo (...) ## pos 2.1.39
# > 
# > , so that it be easy to keep track of the changes.
# > 
# >   Hth,
# > 
# >   Etienne
# > 
# > ======================================================================
# > ;; Keyboard Macro Editor.  Press C-c C-c to finish; press C-x k RET to cancel.
# > ;; Original keys: C-a C-k C-y C-a ## S-SPC pre SPC 2.1.39 SPC C-e RET C-y C-e SPC ## SPC pos SPC 2.1.39
# > 
# > Command: octadapt
# > Key: none
# > 
# > Macro:
# > 
# > C-a			;; beginning-of-line
# > C-k			;; kill-line
# > C-y			;; hilit-yank
# > C-a			;; beginning-of-line
# > ##			;; self-insert-command * 2
# > S-SPC
# > pre			;; self-insert-command * 3
# > SPC			;; self-insert-command
# > 2.1.39			;; self-insert-command * 6
# > SPC			;; self-insert-command
# > C-e			;; end-of-line
# > RET			;; newline
# > C-y			;; hilit-yank
# > C-e			;; end-of-line
# > SPC			;; self-insert-command
# > ##			;; self-insert-command * 2
# > SPC			;; self-insert-command
# > pos			;; self-insert-command * 3
# > SPC			;; self-insert-command
# > 2.1.39			;; self-insert-command * 6
# > 
# > 
# > -- 
# > Etienne Grossmann ------ http://www.isr.ist.utl.pt/~etienne
# > 
# > 
# > -------------------------------------------------------
# > This sf.net email is sponsored by: See the NEW Palm 
# > Tungsten T handheld. Power & Color in a compact size!
# > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
# > _______________________________________________
# > Octave-dev mailing list
# > Oct...@li...
# > https://lists.sourceforge.net/lists/listinfo/octave-dev
# 
# 

-- 
Etienne Grossmann ------ http://www.isr.ist.utl.pt/~etienne

Re: [OctDev] emacs macro for 2.1.39 adaptation

[Paul K. <pki...@ja...>]

Supporting both styles of args will lead to a lot crufty code.  Along with
the rapid developments of the past few months (cell array support and 
keyed list support) we are going to be doing a lot of things differently.

Do we really want to support pre-2.1.38 Octave?

I've already converted functions in general, image and signal, but I can
put backward compatibility support in again if someone wants to take the
time to write the preprocessor.

Please use apps available to configure: cc, grep, awk, sed but no perl,
python or tcl.

To support the TSA toolbox, the preprocessor should also be able to test
for matlab versions.

How about:

	%function foo (...)      %# pre o2.1.37
	function foo (varargin)  %# post o2.1.37 or post m5.0.0
	%function foo (a1,a2,a3,a4,a5) %# pre m5

Or if you don't want to bother with Matlab 4 support

	%function foo (...)      %# pre o2.1.37
	function foo (varargin)  %# post o2.1.37 or post m0

We don't have to write the preprocessor now, but it would be nice to
nail the syntax.  

Call it with 
	mprep o$OCTAVE_VERSION *.m
or
	mprep m$MATLAB_VERSION *.m


So version is nameMajor.Minor.Patch, and we need pre, post, and, or

We could let name be the null string for octave.

Thoughts?

- Paul

On Sat, Nov 02, 2002 at 01:35:29PM +0000, Etienne Grossmann wrote:
> 
>   Hello,
> 
> for those who use emacs and are updating octave code for 2.1.39, the
> following macro may come handy to substitute a line like 
> 
>      function foo (...)
> 
>   into 
> 
>      ## pre 2.1.39 function foo (...)
>      function foo (...) ## pos 2.1.39
> 
> , so that it be easy to keep track of the changes.
> 
>   Hth,
> 
>   Etienne
> 
> ======================================================================
> ;; Keyboard Macro Editor.  Press C-c C-c to finish; press C-x k RET to cancel.
> ;; Original keys: C-a C-k C-y C-a ## S-SPC pre SPC 2.1.39 SPC C-e RET C-y C-e SPC ## SPC pos SPC 2.1.39
> 
> Command: octadapt
> Key: none
> 
> Macro:
> 
> C-a			;; beginning-of-line
> C-k			;; kill-line
> C-y			;; hilit-yank
> C-a			;; beginning-of-line
> ##			;; self-insert-command * 2
> S-SPC
> pre			;; self-insert-command * 3
> SPC			;; self-insert-command
> 2.1.39			;; self-insert-command * 6
> SPC			;; self-insert-command
> C-e			;; end-of-line
> RET			;; newline
> C-y			;; hilit-yank
> C-e			;; end-of-line
> SPC			;; self-insert-command
> ##			;; self-insert-command * 2
> SPC			;; self-insert-command
> pos			;; self-insert-command * 3
> SPC			;; self-insert-command
> 2.1.39			;; self-insert-command * 6
> 
> 
> -- 
> Etienne Grossmann ------ http://www.isr.ist.utl.pt/~etienne
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by: See the NEW Palm 
> Tungsten T handheld. Power & Color in a compact size!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
> _______________________________________________
> Octave-dev mailing list
> Oct...@li...
> https://lists.sourceforge.net/lists/listinfo/octave-dev

[OctDev] emacs macro for 2.1.39 adaptation

[Etienne G. <et...@is...>]

  Hello,

for those who use emacs and are updating octave code for 2.1.39, the
following macro may come handy to substitute a line like 

     function foo (...)

  into 

     ## pre 2.1.39 function foo (...)
     function foo (...) ## pos 2.1.39

, so that it be easy to keep track of the changes.

  Hth,

  Etienne

======================================================================
;; Keyboard Macro Editor.  Press C-c C-c to finish; press C-x k RET to cancel.
;; Original keys: C-a C-k C-y C-a ## S-SPC pre SPC 2.1.39 SPC C-e RET C-y C-e SPC ## SPC pos SPC 2.1.39

Command: octadapt
Key: none

Macro:

C-a			;; beginning-of-line
C-k			;; kill-line
C-y			;; hilit-yank
C-a			;; beginning-of-line
##			;; self-insert-command * 2
S-SPC
pre			;; self-insert-command * 3
SPC			;; self-insert-command
2.1.39			;; self-insert-command * 6
SPC			;; self-insert-command
C-e			;; end-of-line
RET			;; newline
C-y			;; hilit-yank
C-e			;; end-of-line
SPC			;; self-insert-command
##			;; self-insert-command * 2
SPC			;; self-insert-command
pos			;; self-insert-command * 3
SPC			;; self-insert-command
2.1.39			;; self-insert-command * 6


-- 
Etienne Grossmann ------ http://www.isr.ist.utl.pt/~etienne

[OctDev] Re: Error : "not a valid shared library"

[Etienne G. <et...@is...>]

  Hello,

just to say that the "not a valid shared library" error disappeared w/
2.1.39. I'm puzzled.

  Cheers,

  Etienne

On Thu, Oct 31, 2002 at 02:13:20PM +0000, Etienne Grossmann wrote:
# 
# 
#   Hello,
# 
# I am having a problem w/ my octave-forge installation (from cvs) and
# am asking for advice, siggestions & tips.
# 
#   I installed octave-2.1.38 from source this morning. Compilers are
# (exported environment variables) CC=gcc-3.0, CXX=g++-3.0 and
# F77=g77-3.0.
# 
#        make clean ; ./configure ; make 
# 
#   When make failed with a problem in fsolve.cc, I "fixed" it with
# 
#     cp FIXES/kron.oct FIXES/fsolve.oct
#   
#   and then make worked.
# 
#   Then I start octave and put my octave-forge cvs tree in the search
# path and check about an oct-file defined in octave-forge : 
# 
# octave:2> which leval
# error: /home/etienne/prog/octave/octave-forge/octave-forge/main/optim/leval.oct is not a valid shared libr
# which: `leval' is undefined
# 
#   Same for other .oct files (bitor, delaunayn, getfield ...).
# 
#   I had the same problem with gcc-2.95 (and corresponding g++ and
# f77).
# 
#   Linux is Debian 3.0
# 
#   Any ideas on what the problem is?
# 
#   Etienne
# 
#   I 
# 
# -- 
# Etienne Grossmann ------ http://www.isr.ist.utl.pt/~etienne
# 
# 

-- 
Etienne Grossmann ------ http://www.isr.ist.utl.pt/~etienne

Re: [OctDev] Is this where I post questions about compiling octave-forge?

[Paul K. <pki...@ja...>]

I'm betting it is in getfield/setfield for octave 2.1.38.  You don't
actually need these because there are m-file equivalents available.
Just comment them out of the make file for now.  Also John Eaton posted a 
patch on the help-octave mailing list (somewhere off www.octave.org).

In practice you won't need getfield.cc/setfield.cc very long because
you can now say:

	a.(k) = v

where k is the key and v is the value.  I haven't tested the speed
compared to setfield.cc yet.

Paul Kienzle
pki...@us...

  

On Fri, Nov 01, 2002 at 02:46:11PM -0800, Daniel Lyddy wrote:
> All,
> 
> I am having trouble getting octave-forge to compile on Mandrake Linux 
> 9.0.  Is this where I post the details, or can someone give me a link to 
> a more appropriate list?
> 
> Dan
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by: See the NEW Palm 
> Tungsten T handheld. Power & Color in a compact size!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
> _______________________________________________
> Octave-dev mailing list
> Oct...@li...
> https://lists.sourceforge.net/lists/listinfo/octave-dev

[OctDev] Is this where I post questions about compiling octave-forge?

[Daniel L. <spr...@PA...>]

All,

I am having trouble getting octave-forge to compile on Mandrake Linux 
9.0.  Is this where I post the details, or can someone give me a link to 
a more appropriate list?

Dan

[OctDev] Error : "not a valid shared library"

[Etienne G. <et...@is...>]

  Hello,

I am having a problem w/ my octave-forge installation (from cvs) and
am asking for advice, siggestions & tips.

  I installed octave-2.1.38 from source this morning. Compilers are
(exported environment variables) CC=gcc-3.0, CXX=g++-3.0 and
F77=g77-3.0.

       make clean ; ./configure ; make 

  When make failed with a problem in fsolve.cc, I "fixed" it with

    cp FIXES/kron.oct FIXES/fsolve.oct
  
  and then make worked.

  Then I start octave and put my octave-forge cvs tree in the search
path and check about an oct-file defined in octave-forge : 

octave:2> which leval
error: /home/etienne/prog/octave/octave-forge/octave-forge/main/optim/leval.oct is not a valid shared libr
which: `leval' is undefined

  Same for other .oct files (bitor, delaunayn, getfield ...).

  I had the same problem with gcc-2.95 (and corresponding g++ and
f77).

  Linux is Debian 3.0

  Any ideas on what the problem is?

  Etienne

  I 

-- 
Etienne Grossmann ------ http://www.isr.ist.utl.pt/~etienne

[OctDev] Re: Octave 2.1.37 available for ftp

[Dirk E. <ed...@de...>]

For the record, octave-forge built just fine Debian once I applied JWE's
patch to main/struct/{get,set}field.cc.

So as far as Debian is concerned, we have octave-2.1.37 as well as updated
versions of octave-forge and octave-sp in the unstable distribution.

Dirk

-- 
Good judgement comes from experience; experience comes from bad judgement. 
							    -- Fred Brooks

[OctDev] Re: Octave 2.1.37 available for ftp

[Etienne G. <et...@is...>]

On Fri, Oct 25, 2002 at 04:41:30PM -0400, Paul Kienzle wrote:
# I'm getting core dumps when reloading an m-file after editting
# in 2.1.37.  Before I start debugging this, is anyone else
# getting this behaviour?

  Hello,

I have switched back to 2.1.36 until wednesday : I am presenting my
PhD on tuesday, so until then I would rather have a working setup.

  Starting wednesday, I will look more closely at octave-2.1.37 and
octave-forge.

  Etienne 

-- 
Etienne Grossmann ------ http://www.isr.ist.utl.pt/~etienne

Re: [OctDev] Re: Octave 2.1.37 available for ftp

[John W. E. <jw...@be...>]

On 24-Oct-2002, Etienne Grossmann <et...@is...> wrote:

| 
|    Hello,
| 
| 
| 1) The va_arg() change causes tons of messages (any way to turn them
|    off?). On the contrary, the now obsolete is_XXX() cause no fuss at
|    first sight.

You could try

  warning ("off")

but that's a big hammer.  Or you could find the place in Octave where
the warning is issued and remove it.  But I'd rather fix as many of
the va_arg usages as we can now, so that we can delete va_arg
completely from Octave before too long.

| 2) There seem to be a fair amount of broken things

What?

| 3) I am preparing slides for my PhD next week, so I won't be very
|    available for octave-forge until then.

OK.

| Still, I am doing cvs update and will see if I can fix the main/struct
| directory.

I already posted a patch for getfield and setfield.

jwe

Re: [OctDev] Re: Octave 2.1.37 available for ftp

[Etienne G. <et...@is...>]

   Hello,


1) The va_arg() change causes tons of messages (any way to turn them
   off?). On the contrary, the now obsolete is_XXX() cause no fuss at
   first sight.

2) There seem to be a fair amount of broken things

3) I am preparing slides for my PhD next week, so I won't be very
   available for octave-forge until then.

Still, I am doing cvs update and will see if I can fix the main/struct
directory.

  Etienne

On Thu, Oct 24, 2002 at 11:00:12AM -0400, Paul Kienzle wrote:
# On Wed, Oct 23, 2002 at 10:49:04PM +0100, Etienne Grossmann wrote:
# > 
# >   Hello,
# > 
[snip] 
# I say commit directly.  If anything really serious goes wrong we can
# always back out.
# 
# Are we abandoning support for 2.1.36?

  Let's get support to 2.137!
 
# - Paul
# 

-- 
Etienne Grossmann ------ http://www.isr.ist.utl.pt/~etienne