[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 09:47:07 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:76.0) Gecko/20100101 Firefox/76.0

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

What still needs to be done as far as I can see, is (not in any particular
* decide on the non-Matlab extensions in Lars' function (additional fields and
"linux" flag),
* add a branch for Windows platforms to Lars' function (effectively a
"translation" from __wmemory__ to the "memory" output structures),
* add code for Mac platforms (or does the Linux approach also work on Macs?),
* and make a patch for the default branch out of all this.

Did I miss something?

Some Octave extensions over Matlab bit us in the back in the past. I believe
it is best to keep it simple and close to Matlab's behavior unless there is a
big advantage in deviating.
So I'd vote for removing the additional fields and the "linux" flag from Lars'
function and for not implementing the RAM usage check for other processes.
If that is needed, we could use dedicated, separate functions for this. But
these features should be working cross-platform if we do so.


Reply to this item at:


  Message sent via Savannah

reply via email to

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