[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: MinGW
From: |
David Bateman |
Subject: |
Re: MinGW |
Date: |
Tue, 25 Apr 2006 09:43:57 +0200 |
User-agent: |
Mozilla Thunderbird 1.0.6-7.5.20060mdk (X11/20050322) |
John W. Eaton wrote:
>On 24-Apr-2006, David Bateman wrote:
>
>| address@hidden wrote:
>|
>| >Hi David,
>| >
>| >Could I have access to the code that has the fixed "pathsep"? You
>mentioned that it is not in the cvs but it was on your computer.
>| >
>| >
>| >
>|
>| In fact I don't have anything. There is a variable sepchar in Makeconf,
>| and so also in the octave function octave_config_info as SEPCHAR. In
>| fact I believe a function Fsepchar should be added to the code.
>| Something like
>|
>| DEFCONST (sepchar, SEPCHAR_STR,
>| "-*- texinfo -*-\n\
>| @defvr {Built-in Variable} sepchar\n\
>| The character used to separate directories in the path. The\n\
>| value of this variable is system dependent.\n\
>| @seealso{filesep,dir, ls}\n\
>| @end defvr");
>|
>| There are several problem functions for sepchar, including path.m,
>| addpath.m and rmpath.m that hardcodes the ":" as sepchar, while it
>| should use sepchar.
>
>I'm trying to remove DEFCONST/DEFVAR so this should probably be a
>function.
>
>
Ok, with me, the change to the above is minor
>OTOH, maybe we should convert the internals to use an array of
>character strings instead. These could be exported to the scripting
>langage as cell arrays of character strings instead. Then we wouldn't
>need sepchar to deal with Octave's own paths, though we might still
>need it for handling OS PATH variables.
>
>
This would probably require much more work to convert than just adding a
sepchar function and using it in path, addpath and rmpath.
>Maybe we should move this discussion to the maintainers list?
>
>
Ok, with me..
D.
--
David Bateman address@hidden
Motorola Labs - Paris +33 1 69 35 48 04 (Ph)
Parc Les Algorithmes, Commune de St Aubin +33 6 72 01 06 33 (Mob)
91193 Gif-Sur-Yvette FRANCE +33 1 69 35 77 01 (Fax)
The information contained in this communication has been classified as:
[x] General Business Information
[ ] Motorola Internal Use Only
[ ] Motorola Confidential Proprietary
- Re: MinGW,
David Bateman <=