[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: Fri, 1 May 2020 13:33:32 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:76.0) Gecko/20100101 Firefox/76.0

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

>From the code of memory.m, I was under the impression that
user.RamAvailableAllArrays and syst.PhysicalMemory.Available would always have
the same value.
Do I correctly understand that the value for user.RamAvailableAllArrays will
have to be determined differently in the future?
Maybe we could add that field (possibly with a more Octave-y name) once it is
clear how we can get the corresponding information.


Reply to this item at:


  Message sent via Savannah

reply via email to

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