View Issue Details

IDProjectCategoryView StatusLast Update
0000702LDMud 3.5LPC Compiler/Preprocessorpublic2017-10-04 18:57
Reporterzesstra Assigned Tozesstra  
PrioritylowSeverityminorReproducibilityN/A
Status resolvedResolutionfixed 
Target Version3.5.0Fixed in Version3.5.0 
Summary0000702: RfC: Remove some pragmas
DescriptionI thought about some pragmas and if we still need them in 3.5.

+ combine_strings, no_combine_strings: Is there a real advantage of no_combine_strings? Does need the behaviour of no_combine_strings?

+ verbose_errors: would it be harmful to always enable that it? Honest question, I don't even know a program in MG which does not use it.

+ local_scopes, no_local_scopes: Are there still Muds with more than sporadic programs which need no_local_scopes?
TagsNo tags attached.

Activities

_xtian_

2009-11-05 14:51

reporter   ~0001609

Never seen a MUD where this would be a problem.

Additionally I would propose activating warn_deprecated
This means less pain changing the driver and mudlib code in the long run.

zesstra

2009-11-05 15:31

administrator   ~0001611

I think, that suggestion makes sense, because it warns Mud admins and they can turn the warnings off with the auto include hook.

zesstra

2010-02-15 18:17

administrator   ~0001733

Will do so for 3.5.

zesstra

2010-02-16 16:50

administrator   ~0001737

In r2866 - 2868 I removed the pragmas (no_)combine_strings, verbose_errors and (no_)local_scopes. All these are being ignored by the lexxer. The behaviour of combine_strings, verbose_errors and local_scopes is now always enabled.

r2869 enables warn_deprecated by default.

Issue History

Date Modified Username Field Change
2009-11-05 13:56 zesstra New Issue
2009-11-05 13:56 zesstra Status new => feedback
2009-11-05 14:51 _xtian_ Note Added: 0001609
2009-11-05 15:31 zesstra Note Added: 0001611
2010-02-15 18:17 zesstra Note Added: 0001733
2010-02-15 18:17 zesstra Assigned To => zesstra
2010-02-15 18:17 zesstra Status feedback => assigned
2010-02-16 16:50 zesstra Note Added: 0001737
2010-02-16 16:50 zesstra Status assigned => resolved
2010-02-16 16:50 zesstra Resolution open => fixed
2017-10-04 18:57 zesstra Fixed in Version => 3.5.0