|
From: | Nicholas Jankowski |
Subject: | [Octave-bug-tracker] [bug #60729] print_usage within classdef constructor breaks subsequent calls to the class |
Date: | Fri, 4 Jun 2021 20:55:14 -0400 (EDT) |
User-agent: | Mozilla/5.0 (Linux; Android 9; moto g(6)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.88 Mobile Safari/537.36 |
Follow-up Comment #2, bug #60729 (project octave): > it messes with the behavior of the class definition already loaded into memory. so how does it manage that? Shouldn't it be a esad only operation? Variable name collision? Overzealous cleanup? _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?60729> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |