Re: copying BIOS to a file

On Wed, 19 Dec 2007 17:07:13 GMT, H-Man wrote:

> On Tue, 18 Dec 2007 21:54:17 +0000 (UTC), Auric__ wrote:
>
>> On Tue, 18 Dec 2007 20:39:30 GMT,  wrote:
>>
>>> On Tue, 18 Dec 2007 20:09:14 +0000 (UTC), "Auric__"
>>> <not.my.real@[EMAIL PROTECTED]
> wrote:
>>>
>>>>On Tue, 18 Dec 2007 20:07:02 GMT, I wrote:
>>>>
>>>>> All MS BASICs before VB default to single.
>>>>
>>>>Correction: All MS BASICs *that I've dealt with* prior to VB:
>>>>BASIC.EXE, BASICA.EXE, GWBASIC.EXE, the various flavors of QB,
>>>>and IIRC MS Amiga BASIC. I never played with their original
>>>>Altair BASIC or derivatives. (Before my time.)
>>>
>>> And VB defaults to Variant, which IMO, is even stupider than
>>> defaulting to single.  But, I suppose that it's useful for those
>>> who don't know what they are doing.
>>
>> It makes better sense than single IMO, although if *I* were to
>> design a language, the default data type -- if any -- would be the
>> target processor's native integer type. (I don't like variants.
>> Evil.)
>
> One of the reasons I like PureBasic. It defaults to a 32bit
> integer, otherwise defined by the language as a LONG. A 16 bit
> INTEGER is defined as type WORD, to try to avoid confusion. PB uses
> EnableExplicit to check that all variables are Define(d). I can't
> imagine trying to debug anything without it.

I prefer PowerBasic myself. The Windows versions default to signed 
LONG (DOS version defaults to INTEGER, 16 bits) and include both 
signed and unsigned integers. (PowerBasic's WORD is unsigned; 16-bit 
signed int is INTEGER.)

-- 
I may not be rich and famous, but at least I'm not a raving lunatic.