1. binary files ,kudos,RE:new to this
This is a multi-part message in MIME format.
------=_NextPart_000_0005_01C2C640.21B2AE80
charset="iso-8859-1"
Hey all,
Could anyone tell me what "binary files" are? I know we can read and =
write from them but I am not
sure what they are. Are they for machine code programming? What are =
their .ext? What do they
contain?
Also kudos to the archives these days! Especially "Mic", I don't =
really understand the stuff
but I think either him or Matt Lewis (through the COM library) are going =
to push EUPHORIA
past the "3d barrier".=20
And to "new to this", Euphoria is easy to learn, probably the best =
language to learn if you
know absolutely nothing about programming computers. I'm learning C++ in =
college now
and its a pain, there are dozens of data types that you have to know, =
and you have to make
sure you use the right type in the right place, and all kinds of other =
things that make it
complicated(and needlessly so).But I'm way ahead of everyone else in my =
class because I
learned how to program with EUPHORIA. But keep plugging away with it, I =
first started learning
through a program called "Beginners guide to euphoria", just type the =
name in the archives
search box and you should find it, its less than 1 megabyte it should =
take about 3-5 minutes
with 56k modem.
JDUBE
------=_NextPart_000_0005_01C2C640.21B2AE80
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hey all,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2> Could anyone tell me what "binary =
files" are?=20
I know we can read and write from them but I am not</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>sure what they are. Are they for =
machine code=20
programming? What are their .ext? What do they</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>contain?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2> Also kudos to the archives these =
days!=20
Especially "Mic", I don't really understand the stuff</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>but I think either him or Matt Lewis =
(through the=20
COM library) are going to push EUPHORIA</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>past the "3d barrier". </FONT></DIV>
<DIV><FONT face=3DArial size=3D2> And to "new to this", Euphoria =
is easy to=20
learn, probably the best language to learn if you</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>know absolutely nothing about =
programming=20
computers. I'm learning C++ in college now</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>and its a pain, there are dozens of =
data types that=20
you have to know, and you have to make</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>sure you use the right type in the =
right place, and=20
all kinds of other things that make it</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>complicated(and needlessly so).But I'm =
way ahead of=20
everyone else in my class because I</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>learned how to program with EUPHORIA. =
But keep=20
plugging away with it, I first started learning</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>through a program called "Beginners =
guide to=20
euphoria", just type the name in the archives</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>search box and you should find it, its =
less than 1=20
megabyte it should take about 3-5 minutes</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>with 56k modem.</FONT></DIV>
<DIV><FONT face=3DArial=20
size=3D2> &nbs=
p;  =
; =
&=
nbsp; &n=
bsp; =20
JDUBE</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
------=_NextPart_000_0005_01C2C640.21B2AE80--
2. Re: binary files ,kudos,RE:new to this
On Mon, 27 Jan 2003 20:10:26 -0500, <dubetyrant at hotmail.com> wrote:
>
> Hey all,
>
> Could anyone tell me what "binary files" are? I know we can read and
> write from them but I am not
> sure what they are. Are they for machine code programming? What are their
> .ext? What do they
> contain?
> Also kudos to the archives these days! Especially "Mic", I don't really
> understand the stuff
> but I think either him or Matt Lewis (through the COM library) are going
> to push EUPHORIA
> past the "3d barrier". And to "new to this", Euphoria is easy to learn,
> probably the best language to learn if you
> know absolutely nothing about programming computers. I'm learning C++ in
> college now
> and its a pain, there are dozens of data types that you have to know, and
> you have to make
> sure you use the right type in the right place, and all kinds of other
> things that make it
> complicated(and needlessly so).But I'm way ahead of everyone else in my
> class because I
> learned how to program with EUPHORIA. But keep plugging away with it, I
> first started learning
> through a program called "Beginners guide to euphoria", just type the
> name in the archives
> search box and you should find it, its less than 1 megabyte it should
> take about 3-5 minutes
> with 56k modem.
> JDUBE
Strictly speaking a 'binary' file is one that contains non-text characters.
Generally, files can be classified as either text or binary. Text files
contain only text characters (alphabetic, digits, punctuation, and some
special text chars such as TAB, NEWLINE and CARRIGE-RETURN (about 100 or so
of the possible 256 different bytes values). Text files are internally
organized into lines of text. A line is defined as all the characters up to
and including the end-of-line marker. In Microsoft world the end-of-line is
a two-byte sequence of CARRIAGE-RETURN and NEWLINE (#0D0A) but in the unix
world the EOL is just a single NEWLINE (#0A) byte. Binary files can contain
all 256 byte values and their internal structure can be anything at all. In
order to understand the contents of a binary file, you need to know its
structure first. Examples of binary files are bitmaps (.BMP), music (.MP3)
and executable programs (.EXE). Each of these has a structure which is
documented and you must use this to understand their contents. Have a look
at http://www.wotsit.org for a list of standard binary file formats.
--
cheers,
Derek Parnell
3. Re: binary files ,kudos,RE:new to this
Wow,that opens up a whole new world, so thats how these guys make
programs which can read and/or accept different file types? By
understanding how different file types are organized?Unreal.That is
awesome.Thanks for the education!
JDUBE
>
>Strictly speaking a 'binary' file is one that contains non-text characters.
>Generally, files can be classified as either text or binary. Text files
>contain only text characters (alphabetic, digits, punctuation, and some
>special text chars such as TAB, NEWLINE and CARRIGE-RETURN (about 100 or so
>of the possible 256 different bytes values). Text files are internally
>organized into lines of text. A line is defined as all the characters up to
>and including the end-of-line marker. In Microsoft world the end-of-line is
>a two-byte sequence of CARRIAGE-RETURN and NEWLINE (#0D0A) but in the unix
>world the EOL is just a single NEWLINE (#0A) byte. Binary files can contain
>all 256 byte values and their internal structure can be anything at all. In
>order to understand the contents of a binary file, you need to know its
>structure first. Examples of binary files are bitmaps (.BMP), music (.MP3)
>and executable programs (.EXE). Each of these has a structure which is
>documented and you must use this to understand their contents. Have a look
>at http://www.wotsit.org for a list of standard binary file formats.
>
>--
>
>cheers,
>Derek Parnell
>
>
>
>TOPICA - Start your own email discussion group. FREE!
4. Re: binary files ,kudos,RE:new to this
Hi Derek, you wrote:
[...]
> Text files are internally
> organized into lines of text. A line is defined as all the characters up to
> and including the end-of-line marker. In Microsoft world the end-of-line is
> a two-byte sequence of CARRIAGE-RETURN and NEWLINE (#0D0A) but in the unix
> world the EOL is just a single NEWLINE (#0A) byte.
... and in the Mac world the EOL is just a single CARRIAGE-RETURN (#0D) byte.
To complete the confusion, in e-mails, the EOL is a two-byte sequence of
CARRIAGE-RETURN and NEWLINE (#0D0A) -- at least it should be after RFC 2822 --,
regardless of the 'world' in which the e-mail client 'lives'.
[...]
> Have a look
> at http://www.wotsit.org for a list of standard binary file formats.
Very interesting. Thank you!
Best regards,
Juergen
--
/"\ ASCII ribbon campain | while not asleep do
\ / against HTML in | sheep += 1
X e-mail and news, | end while
/ \ and unneeded MIME |
5. Re: binary files ,kudos,RE:new to this
On Tue, 28 Jan 2003 15:05:36 -0300, rforno at tutopia.com wrote:
>A byte has 8 bits and so 256 different characters can be coded into it. =
When
>these characters are in the range of the letters, numbers and special
>characters, plus 'carriage return', 'tab' and 'new line', the file is =
said
>to be of type 'text'. If other characters are allowed, the file is said =
to
>be 'binary'.
Quite true. Also, however the term binary is often used specifically
to mean executable files (as opposed to source code). Particularly if
you see the phrase "Windows binary" it invariably refers to a program
file, not say word (.doc), excel (.xls), bitmap (.bmp) etc files which
are binary files that occur on windows. No biggie, just pointing out a
popular (mis)use of the term I felt you (jdube) should be aware of.
Pete
6. Re: binary files ,kudos,RE:new to this
On Thu, 30 Jan 2003 23:01:30 +0000, Pete Lomax <petelomax at blueyonder.co.uk>
wrote:
>
> On Tue, 28 Jan 2003 15:05:36 -0300, rforno at tutopia.com wrote:
>
>> A byte has 8 bits and so 256 different characters can be coded into it.
>> When
>> these characters are in the range of the letters, numbers and special
>> characters, plus 'carriage return', 'tab' and 'new line', the file is
>> said
>> to be of type 'text'. If other characters are allowed, the file is said
>> to
>> be 'binary'.
>
> Quite true. Also, however the term binary is often used specifically
> to mean executable files (as opposed to source code). Particularly if
> you see the phrase "Windows binary" it invariably refers to a program
> file, not say word (.doc), excel (.xls), bitmap (.bmp) etc files which
> are binary files that occur on windows. No biggie, just pointing out a
> popular (mis)use of the term I felt you (jdube) should be aware of.
>
You're right, Pete. This is a useful bit of info.
This usage evolved from the idea of compiling source code (text files) in
to executable code (binary files). The term 'binaries' has come to mean any
executable file, whether it be a true binary data file or a text file (as
in scripts). For example, a lot of unix scripts, which are text files, are
stored together with compiled code in a '/bin' directory.
--
cheers,
Derek Parnell
