Re: C, standards, and depending on them
- Next message: Daniel Kahlin: "Re: C, standards, and depending on them"
- Previous message: Spiro Trikaliotis: "C, standards, and depending on them (was: New draft version of o65 file format)"
- In reply to: Spiro Trikaliotis: "C, standards, and depending on them (was: New draft version of o65 file format)"
- Next in thread: Daniel Kahlin: "Re: C, standards, and depending on them"
- Reply: Daniel Kahlin: "Re: C, standards, and depending on them"
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
[ attachment ]
On Fri, Apr 01, 2005 at 03:00:39PM +0200, Spiro Trikaliotis wrote:
> In fact, if I really rely on this behaviour (variables being
> initialized), I find it much better if I make this assumption explicit
> by writing the "= 0" after the definition of the variable. It does not
> harm and (hopefully) tells the programmer after me that this was done
> deliberately.
Well actually it does. Usually, initialized variables won't go into the bss
segment (even if they're zero), so the resulting executable gets bigger. This
can be an issue on small platforms, or on platforms with slow disk I/O (the
1541 comes to mind).
Regards
Uz
--
Ullrich von Bassewitz uz@musoftware.de
Message was sent through the cbm-hackers mailing list
- Next message: Daniel Kahlin: "Re: C, standards, and depending on them"
- Previous message: Spiro Trikaliotis: "C, standards, and depending on them (was: New draft version of o65 file format)"
- In reply to: Spiro Trikaliotis: "C, standards, and depending on them (was: New draft version of o65 file format)"
- Next in thread: Daniel Kahlin: "Re: C, standards, and depending on them"
- Reply: Daniel Kahlin: "Re: C, standards, and depending on them"
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
[ attachment ]
Archive generated by hypermail pre-2.1.8.