Tillbaka till svenska Fidonet
English   Information   Debug  
OS2BBS   0/787
OS2DOSBBS   0/580
OS2HW   0/42
OS2INET   0/37
OS2LAN   0/134
OS2PROG   0/36
OS2REXX   0/113
OS2USER-L   207
OS2   0/4784
OSDEBATE   0/18996
PASCAL   0/490
PERL   0/457
PHP   0/45
POINTS   0/405
POLITICS   0/29554
POL_INC   0/14731
PSION   103
R20_ADMIN   1117
R20_AMATORRADIO   0/2
R20_BEST_OF_FIDONET   13
R20_CHAT   0/893
R20_DEPP   0/3
R20_DEV   399
R20_ECHO2   1379
R20_ECHOPRES   0/35
R20_ESTAT   0/719
R20_FIDONETPROG...
...RAM.MYPOINT   0/2
R20_FIDONETPROGRAM   0/22
R20_FIDONET   0/248
R20_FILEFIND   0/24
R20_FILEFOUND   0/22
R20_HIFI   0/3
R20_INFO2   2759
R20_INTERNET   0/12940
R20_INTRESSE   0/60
R20_INTR_KOM   0/99
R20_KANDIDAT.CHAT   42
R20_KANDIDAT   28
R20_KOM_DEV   112
R20_KONTROLL   0/13056
R20_KORSET   0/18
R20_LOKALTRAFIK   0/24
R20_MODERATOR   0/1852
R20_NC   76
R20_NET200   245
R20_NETWORK.OTH...
...ERNETS   0/13
R20_OPERATIVSYS...
...TEM.LINUX   0/44
R20_PROGRAMVAROR   0/1
R20_REC2NEC   534
R20_SFOSM   0/340
R20_SF   0/108
R20_SPRAK.ENGLISH   0/1
R20_SQUISH   107
R20_TEST   2
R20_WORST_OF_FIDONET   12
RAR   0/9
RA_MULTI   106
RA_UTIL   0/162
REGCON.EUR   0/2055
REGCON   0/13
SCIENCE   0/1206
SF   0/239
SHAREWARE_SUPPORT   0/5146
SHAREWRE   0/14
SIMPSONS   0/169
STATS_OLD1   0/2539.065
STATS_OLD2   0/2530
STATS_OLD3   0/2395.095
STATS_OLD4   0/1692.25
SURVIVOR   0/495
SYSOPS_CORNER   0/3
SYSOP   0/84
TAGLINES   0/112
TEAMOS2   0/4530
TECH   0/2617
TEST.444   0/105
TRAPDOOR   0/19
TREK   0/755
TUB   0/290
UFO   0/40
UNIX   0/1316
USA_EURLINK   0/102
USR_MODEMS   0/1
VATICAN   0/2740
VIETNAM_VETS   0/14
VIRUS   0/378
VIRUS_INFO   0/201
VISUAL_BASIC   0/473
WHITEHOUSE   0/5187
WIN2000   0/101
WIN32   0/30
WIN95   0/4276
WIN95_OLD1   0/70272
WINDOWS   0/1517
WWB_SYSOP   0/419
WWB_TECH   0/810
ZCC-PUBLIC   0/1
ZEC   4

 
4DOS   0/134
ABORTION   0/7
ALASKA_CHAT   0/506
ALLFIX_FILE   0/1313
ALLFIX_FILE_OLD1   0/7997
ALT_DOS   0/152
AMATEUR_RADIO   0/1039
AMIGASALE   0/14
AMIGA   0/331
AMIGA_INT   0/1
AMIGA_PROG   0/20
AMIGA_SYSOP   0/26
ANIME   0/15
ARGUS   0/924
ASCII_ART   0/340
ASIAN_LINK   0/651
ASTRONOMY   0/417
AUDIO   0/92
AUTOMOBILE_RACING   0/105
BABYLON5   0/17862
BAG   135
BATPOWER   0/361
BBBS.ENGLISH   0/382
BBSLAW   0/109
BBS_ADS   0/5290
BBS_INTERNET   0/507
BIBLE   0/3563
BINKD   0/1119
BINKLEY   0/215
BLUEWAVE   0/2173
CABLE_MODEMS   0/25
CBM   0/46
CDRECORD   0/66
CDROM   0/20
CLASSIC_COMPUTER   0/378
COMICS   0/15
CONSPRCY   0/899
COOKING   28282
COOKING_OLD1   0/24719
COOKING_OLD2   0/40862
COOKING_OLD3   0/37489
COOKING_OLD4   0/35496
COOKING_OLD5   9370
C_ECHO   0/189
C_PLUSPLUS   0/31
DIRTY_DOZEN   0/201
DOORGAMES   0/2008
DOS_INTERNET   0/196
duplikat   6000
ECHOLIST   0/18295
EC_SUPPORT   0/318
ELECTRONICS   0/359
ELEKTRONIK.GER   1534
ENET.LINGUISTIC   0/13
ENET.POLITICS   0/4
ENET.SOFT   0/11701
ENET.SYSOP   33803
ENET.TALKS   0/32
ENGLISH_TUTOR   0/2000
EVOLUTION   0/1335
FDECHO   0/217
FDN_ANNOUNCE   0/7068
FIDONEWS   23520
FIDONEWS_OLD1   0/49742
FIDONEWS_OLD2   0/35949
FIDONEWS_OLD3   0/30874
FIDONEWS_OLD4   0/37224
FIDO_SYSOP   12841
FIDO_UTIL   0/180
FILEFIND   0/209
FILEGATE   0/212
FILM   0/18
FNEWS_PUBLISH   4186
FN_SYSOP   41525
FN_SYSOP_OLD1   71952
FTP_FIDO   0/2
FTSC_PUBLIC   0/13571
FUNNY   0/4886
GENEALOGY.EUR   0/71
GET_INFO   105
GOLDED   0/408
HAM   0/16052
HOLYSMOKE   0/6791
HOT_SITES   0/1
HTMLEDIT   0/71
HUB203   466
HUB_100   264
HUB_400   39
HUMOR   0/29
IC   0/2851
INTERNET   0/424
INTERUSER   0/3
IP_CONNECT   719
JAMNNTPD   0/233
JAMTLAND   0/47
KATTY_KORNER   0/41
LAN   0/16
LINUX-USER   0/19
LINUXHELP   0/1155
LINUX   0/22010
LINUX_BBS   0/957
mail   18.68
mail_fore_ok   249
MENSA   0/341
MODERATOR   0/102
MONTE   0/992
MOSCOW_OKLAHOMA   0/1245
MUFFIN   0/783
MUSIC   0/321
N203_STAT   898
N203_SYSCHAT   313
NET203   321
NET204   69
NET_DEV   0/10
NORD.ADMIN   0/101
NORD.CHAT   0/2572
NORD.FIDONET   189
NORD.HARDWARE   0/28
NORD.KULTUR   0/114
NORD.PROG   0/32
NORD.SOFTWARE   0/88
NORD.TEKNIK   0/58
NORD   0/453
OCCULT_CHAT   0/93
Möte OSDEBATE, 18996 texter
 lista första sista föregående nästa 
Text 3151, 166 rader
Skriven 2005-03-13 20:17:36 av Rich (1:379/45)
   Kommentar till text 3149 av John Beckett (1:379/45)
Ärende: Re: IDE market consolidates some more...?
=================================================
From: "Rich" <@>

This is a multi-part message in MIME format.

------=_NextPart_000_0525_01C52809.B2ECD790
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   I don't know how to interpret the following statement of yours

  people wanting to write C++ programs will have to
  either write a Win32-compatible program that would run on 32-bit or
  64-bit systems, or would have to write a .NET program that operated
  via the CLR (it too would presumably run on both 32/64 bit).

You use this in reference to some future version of Windows running on a =
64-bit processor.  Why I'm puzzled is this describes today, both 32-bit = and
64-bit.  You can write a native app or a managed app.  I don't see = anything
contentious.  Maybe I'm missing it.

   Back to the earlier bogus claim, it is nothing like your statement =
above and is in direct contrast in some ways.

Rich

  "John Beckett" <FirstLast@compuserve.com.omit> wrote in message =
news:8r0a31tugsae7bepqj991nu50h826n52m7@4ax.com...
  On Sun, 13 Mar 2005 18:01:57 -0800, "Rich" <@> wrote:

  > Actually there was no reference to 64-bit at all so I don't know =
where you got the impression.

  Sorry, I used sloppy words. I was thinking of the future when
  (presumably) the programming model discussed in the MSDN quote is used
  on 64-bit Windows systems.

  >  For what it is worth, Win32 is the name of the API and is not a =
word size designation.
  >  Next, MFC is not a Windows API.

  Thanks, but I am aware of these points. What I inferred from the brief
  MSDN quote is that when some future release of Windows is running on
  64-bit systems, people wanting to write C++ programs will have to
  either write a Win32-compatible program that would run on 32-bit or
  64-bit systems, or would have to write a .NET program that operated
  via the CLR (it too would presumably run on both 32/64 bit).

  I believe this is the point that Mike was making.

  Thinking about it a bit more, I can see that there may be no better
  way for Microsoft to push developers. When we went from 16-bit to
  32-bit machines, it was necessary to (eventually) drop the old APIs
  and use Win32 to take advantage of the environment. It looks as if the
  same will not occur in 64-bit machines, except indirectly via .NET.

  I guess that cleaning up all the API interfaces (for a "win64") just
  wouldn't be worthwhile, at least not for many years.

  OMG - I still wonder how to get the true path name of a file in Win32,
  and live with the forlorn hope that the old systems will be
  redesigned!

  John

------=_NextPart_000_0525_01C52809.B2ECD790
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.3790.1289" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp; I don't know how to =
interpret the=20
following statement of yours</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV><FONT face=3DArial size=3D2><FONT face=3D"Times New Roman" =
size=3D3>people=20
  wanting to write C++ programs will have to<BR>either write a =
Win32-compatible=20
  program that would run on 32-bit or<BR>64-bit systems, or would have =
to write=20
  a .NET program that operated<BR>via the CLR (it too would presumably =
run on=20
  both 32/64 bit).</FONT><BR></FONT></DIV></BLOCKQUOTE>
<DIV><FONT face=3DArial size=3D2>You use this in reference to some =
future version of=20
Windows running on a 64-bit processor.&nbsp; Why I'm puzzled is this =
describes=20
today, both 32-bit and 64-bit.&nbsp; You can write a native app or a =
managed=20
app.&nbsp; I don't see anything contentious.&nbsp; Maybe I'm missing=20
it.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp; Back to the earlier bogus =
claim, it is=20
nothing like your statement above and is in direct contrast in some=20
ways.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Rich</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV>"John Beckett" &lt;<A=20
  =
href=3D"mailto:FirstLast@compuserve.com.omit">FirstLast@compuserve.com.om=
it</A>&gt;=20
  wrote in message <A=20
  =
href=3D"news:8r0a31tugsae7bepqj991nu50h826n52m7@4ax.com">news:8r0a31tugsa=
e7bepqj991nu50h826n52m7@4ax.com</A>...</DIV>On=20
  Sun, 13 Mar 2005 18:01:57 -0800, "Rich" &lt;@&gt; wrote:<BR><BR>&gt; =
Actually=20
  there was no reference to 64-bit at all so I don't know where you got =
the=20
  impression.<BR><BR>Sorry, I used sloppy words. I was thinking of the =
future=20
  when<BR>(presumably) the programming model discussed in the MSDN quote =
is=20
  used<BR>on 64-bit Windows systems.<BR><BR>&gt;&nbsp; For what it is =
worth,=20
  Win32 is the name of the API and is not a word size =
designation.<BR>&gt;&nbsp;=20
  Next, MFC is not a Windows API.<BR><BR>Thanks, but I am aware of these =
points.=20
  What I inferred from the brief<BR>MSDN quote is that when some future =
release=20
  of Windows is running on<BR>64-bit systems, people wanting to write =
C++=20
  programs will have to<BR>either write a Win32-compatible program that =
would=20
  run on 32-bit or<BR>64-bit systems, or would have to write a .NET =
program that=20
  operated<BR>via the CLR (it too would presumably run on both 32/64=20
  bit).<BR><BR>I believe this is the point that Mike was =
making.<BR><BR>Thinking=20
  about it a bit more, I can see that there may be no better<BR>way for=20
  Microsoft to push developers. When we went from 16-bit to<BR>32-bit =
machines,=20
  it was necessary to (eventually) drop the old APIs<BR>and use Win32 to =
take=20
  advantage of the environment. It looks as if the<BR>same will not =
occur in=20
  64-bit machines, except indirectly via .NET.<BR><BR>I guess that =
cleaning up=20
  all the API interfaces (for a "win64") just<BR>wouldn't be worthwhile, =
at=20
  least not for many years.<BR><BR>OMG - I still wonder how to get the =
true path=20
  name of a file in Win32,<BR>and live with the forlorn hope that the =
old=20
  systems will =
be<BR>redesigned!<BR><BR>John<BR></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0525_01C52809.B2ECD790--

--- BBBS/NT v4.01 Flag-5
 * Origin: Barktopia BBS Site http://HarborWebs.com:8081 (1:379/45)