View Issue Details

IDProjectCategoryView StatusLast Update
0000176LDMudLPC Compiler/Preprocessorpublic2009-10-05 18:41
ReporterlarsAssigned To 
PrioritynormalSeverityfeatureReproducibilityN/A
Status newResolutionopen 
Summary0000176: #pragma reserve_efun_names
DescriptionShort: #pragma reserve_efun_names
From: Matthew Julius <julius.2@wright.edu>
Date: Fri, 08 Jan 1999 16:29:08 -0500
Type: Feature
State: Unclassified

pragma to 'reserve' [s]efun names
  For example, the following code compiles fine,
    void go() {
      int member;
      member = member(map, 1);
      ...
    }
  Whereas this will not,
    #pragma reserve_efun_names
    void go() {
      int member;
      ...
    }
  This obviously should not affect overloading [s]efuns. This is also
  limited to compile time only.
TagsNo tags attached.
External Data (URL)

Activities

zesstra

2009-10-02 05:25

administrator   ~0001400

Mhmmm. Using variables called like efuns irritates me as well, when reading code. Sometimes it even happens to me by accident, e.g. in case of min,max. So I would welcome it to optionally disallow that. Maybe even including it into 'pedantic'?

Largo

2009-10-02 05:28

reporter   ~0001401

Very good point. Agreed.

zesstra

2009-10-05 18:41

administrator   ~0001478

Mhmm. An issue concerning sefuns: they are more volatile than efuns and may appear and disappear even during an uptime. Should they be included in here?

Issue History

Date Modified Username Field Change
2004-11-26 22:17 lars New Issue
2009-10-02 05:25 zesstra Note Added: 0001400
2009-10-02 05:28 Largo Note Added: 0001401
2009-10-05 18:41 zesstra Note Added: 0001478