[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Understanding how octave displays arrays
|
From: |
Jordi Gutiérrez Hermoso |
|
Subject: |
Re: Understanding how octave displays arrays |
|
Date: |
Mon, 9 Apr 2012 23:16:31 -0400 |
2012/4/9 Corbin Champion <address@hidden>:
> Generally, what my patches are solving are deficiencies of the toolchain.
Then patch the toolchain, not Octave.
The problem with those variables is that it becomes an endless chase
for system-specific behaviour for tons of systems. We don't have
#ifdef __APPLE___ and #ifdef __OPENBSD__ and #ifdef __SOLARIS__. We
have #ifdef __HDF5__ and #ifdef __SLASHPROC__ or whatever else. We do
have #ifdef WIN32, but I think that's a bad idea too, although I don't
know how to fix it just yet.
The GNU build system allows for testing for functionality. Look at
configure.ac in the top-level directory if you want to add another
test.
- Jordi G. H.