[Tutor] bits taken by variable type

Cameron Stoner wolf_binary@hotmail.com
Wed, 26 Jun 2002 09:40:32 -0500


This is a multi-part message in MIME format.

------=_NextPart_000_003E_01C21CF5.83E6C720
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable



I guess I would prefer portable psuedo code, because I would be able to =
work on it without being on a computer.  Its a tough call for me to =
make.  If you have a protable assembler then you don't have to write it =
all again.  Say you format a floppy on a Win machine, can you then use =
it in a Linux machine or a Mac?  I was under the imprecion that the =
machines would recognize the format.  I used to be that way on a Mac in =
the late 90's.  I haven't used a Mac since though.

Thanks everyone,
Cameron Stoner
  ----- Original Message -----=20
  From: alan.gauld@bt.com=20
  To: wolf_binary@hotmail.com ; alan.gauld@bt.com ; tutor@python.org=20
  Sent: Monday, June 24, 2002 9:01 AM
  Subject: RE: [Tutor] bits taken by variable type


  >  You can make a program on a Windows machine then transfer it to a =
Linux =20
  >  machine and as long as it doesn't have any platform specific =
programming =20
  >  in it or has been resolved to not have any conflicts I would think =
you could =20
  >  just use it on both machines.=20

  You can do the same with C/C++  but there are more platform=20
  specifics to fall over. But if you write a sort routine or=20
  number crunching program they will work just fine on either
  platform ONCE YOU HAVE COMPILED THEM.

  But having a compiler on each platform is not so very=20
  different from having Python installed...

  The differences are when you get into things like OS calls to files, =
sockets etc.
  Python masks many of those differences behind the os and socket =
modules

  Which do you prefer, portable assembler or portable pseudo code?

  Alan G.=20

------=_NextPart_000_003E_01C21CF5.83E6C720
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.2713.1100" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I guess I would prefer portable psuedo =
code,=20
because I would be able to work on it without being on a computer.&nbsp; =
Its a=20
tough call for me to make.&nbsp; If you have a protable assembler then =
you don't=20
have to write it all again.&nbsp; Say you format a floppy on a Win =
machine, can=20
you then use it in a Linux machine or a Mac?&nbsp; I was under the =
imprecion=20
that the machines would recognize the format.&nbsp; I used to be that =
way on a=20
Mac in the late 90's.&nbsp; I haven't used a Mac since =
though.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thanks everyone,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Cameron Stoner</FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A title=3Dalan.gauld@bt.com=20
  href=3D"mailto:alan.gauld@bt.com">alan.gauld@bt.com</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Dwolf_binary@hotmail.com=20
  href=3D"mailto:wolf_binary@hotmail.com">wolf_binary@hotmail.com</A> ; =
<A=20
  title=3Dalan.gauld@bt.com =
href=3D"mailto:alan.gauld@bt.com">alan.gauld@bt.com</A>=20
  ; <A title=3Dtutor@python.org=20
  href=3D"mailto:tutor@python.org">tutor@python.org</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Monday, June 24, 2002 =
9:01 AM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> RE: [Tutor] bits taken =
by=20
  variable type</DIV>
  <DIV><BR></DIV>
  <DIV><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D670570014-24062002><FONT=20
  face=3D"Courier New" color=3D#0000ff>&gt; &nbsp;</FONT></SPAN>You can =
make a=20
  program on a Windows machine then transfer it to a Linux&nbsp;<SPAN=20
  class=3D670570014-24062002><FONT face=3D"Courier New"=20
  color=3D#0000ff>&nbsp;</FONT></SPAN></FONT></FONT></DIV>
  <DIV><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D670570014-24062002><FONT=20
  face=3D"Courier New" color=3D#0000ff>&gt; </FONT>&nbsp;</SPAN>machine =
and as long=20
  as it doesn't have any platform specific programming&nbsp;<SPAN=20
  class=3D670570014-24062002><FONT face=3D"Courier New"=20
  color=3D#0000ff>&nbsp;</FONT></SPAN></FONT></FONT></DIV>
  <DIV><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D670570014-24062002><FONT=20
  face=3D"Courier New" color=3D#0000ff>&gt; </FONT>&nbsp;</SPAN>in it or =
has been=20
  resolved to not have any conflicts I would think you could&nbsp;<SPAN=20
  class=3D670570014-24062002><FONT face=3D"Courier New"=20
  color=3D#0000ff>&nbsp;</FONT></SPAN></FONT></FONT></DIV>
  <DIV><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D670570014-24062002><FONT=20
  face=3D"Courier New" color=3D#0000ff>&gt; </FONT>&nbsp;</SPAN>just use =
it on both=20
  machines.<SPAN class=3D670570014-24062002><FONT face=3D"Courier New"=20
  color=3D#0000ff>&nbsp;</FONT></SPAN></FONT></FONT></DIV>
  <DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
  class=3D670570014-24062002></SPAN></FONT></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D670570014-24062002><FONT=20
  face=3D"Courier New" color=3D#0000ff>You can do the same with=20
  C/C++</FONT>&nbsp;<FONT face=3D"Courier New" color=3D#0000ff> but =
there are more=20
  platform </FONT></SPAN></FONT></FONT></DIV>
  <DIV><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D670570014-24062002><FONT=20
  face=3D"Courier New" color=3D#0000ff>specifics to fall over. But if =
you write a=20
  sort routine or </FONT></SPAN></FONT></FONT></DIV>
  <DIV><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D670570014-24062002><FONT=20
  face=3D"Courier New" color=3D#0000ff>number crunching program they =
will work just=20
  fine on either</FONT></SPAN></FONT></FONT></DIV>
  <DIV><FONT face=3D"Courier New" color=3D#0000ff size=3D2><SPAN=20
  class=3D670570014-24062002>platform ONCE YOU HAVE COMPILED=20
  THEM.</SPAN></FONT></DIV>
  <DIV><FONT face=3D"Courier New" color=3D#0000ff size=3D2><SPAN=20
  class=3D670570014-24062002></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3D"Courier New" color=3D#0000ff size=3D2><SPAN=20
  class=3D670570014-24062002>But having a compiler on each platform is =
not so very=20
  </SPAN></FONT></DIV>
  <DIV><FONT face=3D"Courier New" color=3D#0000ff size=3D2><SPAN=20
  class=3D670570014-24062002>different from having Python=20
  installed...</SPAN></FONT></DIV>
  <DIV><FONT face=3D"Courier New" color=3D#0000ff size=3D2><SPAN=20
  class=3D670570014-24062002></SPAN></FONT><FONT face=3DArial=20
  size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN class=3D670570014-24062002>The =
differences=20
  are when you get into things like OS calls to files, sockets=20
  etc.</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN =
class=3D670570014-24062002>Python masks many=20
  of those differences behind the os and socket =
modules</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN=20
  class=3D670570014-24062002></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN =
class=3D670570014-24062002><SPAN=20
  class=3D670570014-24062002>Which do you prefer, portable assembler or =
portable=20
  pseudo code?</SPAN></SPAN></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN=20
  class=3D670570014-24062002></SPAN></FONT>&nbsp;</DIV>
  <DIV><SPAN class=3D670570014-24062002></SPAN><FONT face=3DArial><FONT=20
  size=3D2>A<SPAN class=3D670570014-24062002><FONT face=3D"Courier New"=20
  color=3D#0000ff>lan=20
G.&nbsp;</FONT></SPAN></FONT></FONT></DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_003E_01C21CF5.83E6C720--