Re: Strong typing vs. strong testing

2010-09-28 Thread Malcolm McLean
On Sep 27, 7:46 pm, namekuseijin namekusei...@gmail.com wrote: On 27 set, 05:46, TheFlyingDutchman zzbba...@aol.com wrote: Fact is: almost all user data from the external words comes into programs as strings. No typesystem or compiler handles this fact all that graceful...- Hide quoted text

Re: Strong typing vs. strong testing

2010-09-28 Thread Malcolm McLean
On Sep 27, 9:29 pm, p...@informatimago.com (Pascal J. Bourguignon) wrote: On the other hand, with the dynamic typing mindset, you might even wrap your values (of whatever numerical type) in a symbolic expression mentionning the unit and perhaps other meta data, so that when the other module

Re: Strong typing vs. strong testing

2010-09-28 Thread Malcolm McLean
On Sep 28, 12:19 pm, Tim Bradshaw t...@tfeb.org wrote: There are several existing systems which do this.  The HP48 (and descendants I expect) support units which are essentially dimensions.  I don't remember if it signals errors for incoherent dimensions.   Mathematica also has some units

Re: How far can stack [LIFO] solve do automatic garbage collection and prevent memory leak ?

2010-08-20 Thread Malcolm McLean
On Aug 19, 2:14 pm, spinoza spinoza1...@yahoo.com wrote: All the rest [how to implement heaps] is detail for the little techies to normally, get wrong. That's a fundamental feature of structured programming. If we maintain the interface malloc(), realloc(), and free(), then we could have a

Re: How far can stack [LIFO] solve do automatic garbage collection and prevent memory leak ?

2010-08-16 Thread Malcolm McLean
On Aug 16, 10:20 am, Standish P stnd...@gmail.com wrote: [Q] How far can stack [LIFO] solve do automatic garbage collection and prevent memory leak ? Most programs can be written so that most of their memory allocations are matched by destructors at the same level. However the allocations that

Re: How far can stack [LIFO] solve do automatic garbage collection and prevent memory leak ?

2010-08-16 Thread Malcolm McLean
On Aug 16, 3:14 pm, spinoza spinoza1...@yahoo.com wrote: To build an explicit stack in this program would have been folly, for it would have been necessary to either preallocate the stack and thus legislate the maximum complexity of source code, or use a lot of memory management in the