[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #58345] Emit error and don't parse scripts > 1
From: |
anonymous |
Subject: |
[Octave-bug-tracker] [bug #58345] Emit error and don't parse scripts > 1GB in size |
Date: |
Tue, 12 May 2020 19:36:57 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:76.0) Gecko/20100101 Firefox/76.0 |
Follow-up Comment #4, bug #58345 (project octave):
OP here. I do not have access to Matlab, but the solution you've outlined is
very reasonable.
I was writing them as scripts in the first place because I found that textscan
or fgetl or techniques were the bottleneck in my application, and formatting
it as a script to have the interpreter directly inhale the data as a named
variable was faster, but it of course was not meant to do that for large data.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?58345>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #58345] Crash on executing a 1GB script file, anonymous, 2020/05/10
- [Octave-bug-tracker] [bug #58345] Crash on executing a 1GB script file, Rik, 2020/05/12
- [Octave-bug-tracker] [bug #58345] Crash on executing a 1GB script file, Guillaume, 2020/05/12
- [Octave-bug-tracker] [bug #58345] Emit error and don't parse scripts > 1GB in size, Rik, 2020/05/12
- [Octave-bug-tracker] [bug #58345] Emit error and don't parse scripts > 1GB in size,
anonymous <=
- [Octave-bug-tracker] [bug #58345] Emit error and don't parse scripts > 1GB in size, Rik, 2020/05/12
- [Octave-bug-tracker] [bug #58345] Emit error and don't parse scripts > 1GB in size, Rik, 2020/05/12
- [Octave-bug-tracker] [bug #58345] Emit error and don't parse scripts > 1GB in size, anonymous, 2020/05/13
- [Octave-bug-tracker] [bug #58345] Emit error and don't parse scripts > 1GB in size, Rik, 2020/05/26