[Octave-bug-tracker] [bug #51377] Parse error for abstract methods

[Piotr Held]

Follow-up Comment #1, bug #51377 (project octave):

The way I solved this problem is I created a lexical_feedback flag called
looking_at_abstract_attribute_block. This is true when an attr (in
oct-parse.in.yy) with name "Abstract" appears (or an assignment
"Abstract = true"). If the flag is true then
base_parser::start_classdef_external_method creates a dummy function for the
abstract method and everything parses correctly (just as it would if the
abstract class was in an @-folder). 

I will open a separate bug that concerns the fact that you can instantiate
abstract classes (even now if placed in @-folders an abstract class can be
instantiated). I will attempt to solve that problem if the solution to this
problem is acceptable.

I also added tests for this particular problem.

(file #41527)
    _______________________________________________________

Additional Item Attachment:

File name: patch_bug51377.diff            Size:6 KB


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?51377>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/