[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: What to do with builtin functions not in libinterp subdirectory
From: |
Jordi Gutiérrez Hermoso |
Subject: |
Re: What to do with builtin functions not in libinterp subdirectory |
Date: |
Mon, 18 Mar 2013 12:25:44 -0400 |
On 18 March 2013 12:14, Daniel J Sebald <address@hidden> wrote:
> once you have a prototype function designed in C++, one could
> write an Octave script that scans the source tree replacing all XDEFUNs,
> then DEFUNs, etc. with the new prototype.
I like the idea in principle of replacing CPP macros with C++ classes,
and I have undertaken such macro-slaying quests in the past. However,
I think in this case writing some script to do the conversion cleanly
might be more work than ad-hoc methods. Don't let that discourage you,
though. I like this idea a lot.
- Jordi G. H.
- What to do with builtin functions not in libinterp subdirectory, Daniel J Sebald, 2013/03/18
- Re: What to do with builtin functions not in libinterp subdirectory, Daniel J Sebald, 2013/03/18
- Re: What to do with builtin functions not in libinterp subdirectory, Daniel J Sebald, 2013/03/18
- Re: What to do with builtin functions not in libinterp subdirectory,
Jordi Gutiérrez Hermoso <=
- Re: What to do with builtin functions not in libinterp subdirectory, John W. Eaton, 2013/03/18
- Re: What to do with builtin functions not in libinterp subdirectory, Daniel J Sebald, 2013/03/18
- Re: What to do with builtin functions not in libinterp subdirectory, John W. Eaton, 2013/03/18
- Re: What to do with builtin functions not in libinterp subdirectory, Daniel J Sebald, 2013/03/18
- Re: What to do with builtin functions not in libinterp subdirectory, John W. Eaton, 2013/03/18
- Re: What to do with builtin functions not in libinterp subdirectory, Daniel J Sebald, 2013/03/19
- Re: What to do with builtin functions not in libinterp subdirectory, Daniel J Sebald, 2013/03/18