[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-patch-tracker] [patch #9924] Suggestion for a memory() function

From: Markus Mützel
Subject: [Octave-patch-tracker] [patch #9924] Suggestion for a memory() function
Date: Sat, 2 May 2020 11:10:57 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:76.0) Gecko/20100101 Firefox/76.0

Follow-up Comment #16, patch #9924 (project octave):

@Lars: That sounds reasonable.
Maybe we could use underscores "_" in the field name to make it even clearer
that this is an Octave extension. AFAIK, jwe is no big fan of CamelCase.
So what about "RAM_available_all_arrays"?

The 3 GiB for the total user address space on 32bit systems seems to be hard
coded. If I correctly understood, that might be different for kernels compiled
with non-default settings. Is there an interface to query the actual value on
For Windows, this is probably the value of sys.TotalVirtual.


Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]