[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Problem with glob <=> rpl_glob
From: |
John W. Eaton |
Subject: |
Re: Problem with glob <=> rpl_glob |
Date: |
Wed, 20 Jan 2010 11:07:31 -0500 |
On 20-Jan-2010, Michael Goffioul wrote:
| 2010/1/20 John W. Eaton <address@hidden>:
| > |
| > | I thought about doing that, but decided to use the following change
| > | instead.
| > |
| > | http://hg.savannah.gnu.org/hgweb/octave
| >
| > Sorry, I hit send too quickly. I meant this change:
| >
| > http://hg.savannah.gnu.org/hgweb/octave/rev/805a83ecd3da
|
| Slightly more complex solution :)
|
| I'll test asap, but just one comment: could you tag the new
| functions with OCTAVE_API?
Why is that needed? These functions should not be called outside of
the library itself. The interface for liboctave is still the
glob_match class. I only used a separate file and functions to avoid
the #dfefine problem.
jwe
- Problem with glob <=> rpl_glob, Michael Goffioul, 2010/01/17
- Problem with glob <=> rpl_glob, John W. Eaton, 2010/01/17
- Re: Problem with glob <=> rpl_glob, Michael Goffioul, 2010/01/18
- Re: Problem with glob <=> rpl_glob, John W. Eaton, 2010/01/20
- Re: Problem with glob <=> rpl_glob, John W. Eaton, 2010/01/20
- Re: Problem with glob <=> rpl_glob, Michael Goffioul, 2010/01/20
- Re: Problem with glob <=> rpl_glob,
John W. Eaton <=
- Re: Problem with glob <=> rpl_glob, Michael Goffioul, 2010/01/20
- Re: Problem with glob <=> rpl_glob, John W. Eaton, 2010/01/20