[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #47320] new function devnull
From: |
Lachlan Andrew |
Subject: |
[Octave-bug-tracker] [bug #47320] new function devnull |
Date: |
Fri, 25 Mar 2016 03:56:12 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:43.0) Gecko/20100101 Firefox/43.0 |
Follow-up Comment #6, bug #47320 (project octave):
Would this be for the benefit of users or of core Octave scripts? Rik's
observations seem mainly relevant if the goal is to reduce the code size of
Octave itself.
Python is used for many systems tasks, and so it is natural that it would need
this more often than Octave does. I can't think of any applications for which
Octave is a natural choice that would use this.
However perhaps it could be part of a system-specific structure variable, with
all sorts of OS/machine/compilation-specific variables, like file-separator,
case-sensitivity of file names, endian-ness, 64-bit indexing etc.
Is there already a structure like that? How can a .m file find out that
information?
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?47320>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/