View Issue Details

IDProjectCategoryView StatusLast Update
0000523LDMud 3.3Runtimepublic2018-01-29 22:57
ReporterGnomi Assigned ToGnomi  
PrioritynormalSeverityfeatureReproducibilityalways
Status resolvedResolutionfixed 
Platformi686OSDebian GNU/LinuxOS Version3.1
Product Version3.3 
Fixed in Version3.3.717 
Summary0000523: The "object to closure was bound to has been destructed" errors shouldn't occur anymore
DescriptionAs closures referencing destructed objects should be handled as zeroes there should be no "object to closure was bound to has been destructed" errors.

They still occur with ERQ callbacks and could be circumvented there with a check_object call. But why not remove this error entirely and let call_lambda just return a zero on the stack?

Greetings,
Gnomi.
TagsNo tags attached.

Activities

Gnomi

2008-07-10 04:18

manager   ~0000713

Any objections to the entire removal of this error message?

zesstra

2008-07-10 04:59

administrator   ~0000714

No, I agree, that this condition should be treated consistently.

BTW: Could we change check_object from a define to a static inline function? There is no difference in the code modern compilers generate, but it is beneficial for debugging.

Gnomi

2008-07-17 03:53

manager   ~0000742

Done as r2392.

Issue History

Date Modified Username Field Change
2008-01-04 19:43 Gnomi New Issue
2008-06-30 05:03 Gnomi Status new => assigned
2008-06-30 05:03 Gnomi Assigned To => Gnomi
2008-07-10 04:18 Gnomi Note Added: 0000713
2008-07-10 04:59 zesstra Note Added: 0000714
2008-07-17 03:53 Gnomi Status assigned => resolved
2008-07-17 03:53 Gnomi Fixed in Version => 3.3.717
2008-07-17 03:53 Gnomi Resolution open => fixed
2008-07-17 03:53 Gnomi Note Added: 0000742
2009-04-14 14:14 zesstra Project LDMud => LDMud 3.3
2010-11-16 10:42 Gnomi Source_changeset_attached => ldmud.git master 500fa9dd
2018-01-29 19:59 Gnomi Source_changeset_attached => ldmud.git master 500fa9dd
2018-01-29 22:57 Gnomi Source_changeset_attached => ldmud.git master 500fa9dd