Subject:
|
Re: Are there GOTO statements in NQC?
|
Newsgroups:
|
lugnet.robotics
|
Date:
|
Thu, 20 Nov 2003 23:56:59 GMT
|
Original-From:
|
Steve Baker <sjbaker1@airmail.netSTOPSPAMMERS>
|
Viewed:
|
1063 times
|
| |
| |
T. Alexander Popiel wrote:
> This exact same argument can be applied to high-level languages
> where you dynamically allocate memory or other resources that need
> to be released before leaving the function.
Which is why we have C++.
With memory constructors and destructors, quite complex resources can be
automatically and cleanly free'd up on exit from a function.
---------------------------- Steve Baker -------------------------
HomeEmail: <sjbaker1@airmail.net> WorkEmail: <sjbaker@link.com>
HomePage : http://www.sjbaker.org
Projects : http://plib.sf.net http://tuxaqfh.sf.net
http://tuxkart.sf.net http://prettypoly.sf.net
-----BEGIN GEEK CODE BLOCK-----
GCS d-- s:+ a+ C++++$ UL+++$ P--- L++++$ E--- W+++ N o+ K? w--- !O M-
V-- PS++ PE- Y-- PGP-- t+ 5 X R+++ tv b++ DI++ D G+ e++ h--(-) r+++ y++++
-----END GEEK CODE BLOCK-----
|
|
Message has 1 Reply: | | Re: Are there GOTO statements in NQC?
|
| (...) *snicker* I'm surprised you used C as one of your example languages, then. Anyway, not all of us are so lucky as to be able to choose a language where you can hide all your cleanup code like that. As a personal issue, I find such cleanup (...) (21 years ago, 21-Nov-03, to lugnet.robotics)
|
Message is in Reply To:
| | Re: Are there GOTO statements in NQC?
|
| (...) This exact same argument can be applied to high-level languages where you dynamically allocate memory or other resources that need to be released before leaving the function. While I agree that forcing people to have only one exit point at all (...) (21 years ago, 20-Nov-03, to lugnet.robotics)
|
19 Messages in This Thread:
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|