Menu
▾
▴
comp-hist-devel — This list is for discussion regarding development of the comp-hist project.
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(105) |
Sep
(33) |
Oct
(8) |
Nov
(30) |
Dec
(15) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(1) |
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(8) |
| 2007 |
Jan
(1) |
Feb
(3) |
Mar
(1) |
Apr
(5) |
May
(7) |
Jun
(7) |
Jul
(5) |
Aug
(38) |
Sep
(15) |
Oct
(13) |
Nov
(12) |
Dec
(3) |
| 2008 |
Jan
(5) |
Feb
(5) |
Mar
(30) |
Apr
(26) |
May
(21) |
Jun
(12) |
Jul
(22) |
Aug
(12) |
Sep
(10) |
Oct
(9) |
Nov
(13) |
Dec
(5) |
| 2009 |
Jan
(74) |
Feb
(49) |
Mar
(10) |
Apr
(35) |
May
(99) |
Jun
(75) |
Jul
(43) |
Aug
(16) |
Sep
(24) |
Oct
(38) |
Nov
(7) |
Dec
(5) |
| 2010 |
Jan
|
Feb
|
Mar
(36) |
Apr
(57) |
May
(73) |
Jun
(59) |
Jul
(54) |
Aug
(57) |
Sep
(26) |
Oct
(3) |
Nov
|
Dec
|
| 2011 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Hans B P. <ha...@di...> - 2000-09-02 19:05:34
|
Kurt Raschke wrote: > > The C parser in CVS fails to compile: This problem is fixed - it was a currupted upload. > [kurt@linux new]$ make html > cc -o html html.c This one you need to link with parser so cc should read cc -o html html.c parser.c New files available as <ftp://aconit.org/pub/files.tgz> I downloaded the file, expanded it and built and tested the sources on my Mandrake 70 system, all seemed OK. Regards -- Hans B Pufal |
|
From: Hans B P. <ha...@di...> - 2000-09-02 08:53:17
|
Kurt Raschke wrote: > [kurt@linux new]$ make parser > cc parser.c -o parser > parser.c: In function `get_line': > parser.c:111: `by' undeclared (first use in this function) > parser.c:111: (Each undeclared identifier is reported only once > parser.c:111: for each function it appears in.) > make: *** [parser] Error 1 This is a corruption presumably on the upload, I get the same problem when I download and I see a difference between my master copy and the downloaded one. One more check to do when uploading files - check that you can download a good copy! Oh and the mlist.ccc file also appears corrupt - duh!!! I will put up a .tgz file directly off my linux box later on taday, at least then any corruptions will be flagged by gzip. > [kurt@linux new]$ make html > cc -o html html.c > /tmp/ccU0bnzp.o: In function `main': > /tmp/ccU0bnzp.o(.text+0xa2): undefined reference to `parse_files' > collect2: ld returned 1 exit status > make: *** [html] Error 1 avn't seen this specific issue, but I will try it before doing the upload later today. Regards (and apologies) -- Hans B Pufal |
|
From: Kurt R. <ku...@ra...> - 2000-08-30 17:02:33
|
The C parser in CVS fails to compile: [kurt@linux new]$ make cc -o html html.c /tmp/cciPM1HH.o: In function `main': /tmp/cciPM1HH.o(.text+0xa2): undefined reference to `parse_files' collect2: ld returned 1 exit status make: *** [all] Error 1 [kurt@linux new]$ make parser cc parser.c -o parser parser.c: In function `get_line': parser.c:111: `by' undeclared (first use in this function) parser.c:111: (Each undeclared identifier is reported only once parser.c:111: for each function it appears in.) make: *** [parser] Error 1 [kurt@linux new]$ make html cc -o html html.c /tmp/ccU0bnzp.o: In function `main': /tmp/ccU0bnzp.o(.text+0xa2): undefined reference to `parse_files' collect2: ld returned 1 exit status make: *** [html] Error 1 |
|
From: <ma...@na...> - 2000-08-30 16:23:46
|
Below is the result of your feedback form. It was submitted by Mason Brown (ma...@na...) on Wednesday, August 30, 2000 at 09:23:42 --------------------------------------------------------------------------- type: add othersubj: SGI nodes: SGI message: Hey there - cool idea with your computer history map. Just wanted to remind you of a little company called SGI. :) All kinds of cool computer history there. -Mason --------------------------------------------------------------------------- REMOTE_ADDR: 24.1.117.130 HTTP_USER_AGENT: Mozilla/4.74 (Macintosh; U; PPC) |
|
From: Scott F. <sj...@ra...> - 2000-08-30 12:58:02
|
Yes, it really happened. -- -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.0.2 (GNU/Linux) Comment: For info see http://www.gnupg.org mQGiBDmoHL8RBACt7yc65iKzR4IW2kKF0wjfZlRVwcwEws6HueM9uKF6HCzyFtyM XJiHz8f3LI2NY/GedfF+XTFc2zQlPummiOrHfAx9Y2hV4ajEpxNgqm36BT21vLuI iTB6roHHm+EiK9dRINyc+kB4v5QV5S9BGxPuygm/3yLZLmGH6RUmSxis1wCgvGnX n3qhbP7Yf/mLO1Du3oEJhR8EAI+TFhyxg3y2xv++xCxKOL9ofF+wPA4EkXPCAokW 10hDmeGY246wOMPWC0Hou1QJqqRN82n5BbJAzUnE/Iht82SEJgM1vhIbp0uShUdS jzKPnBBUTzLQFPbAG9hDaU/98JklsyDIbacavCuCtky6Xs/wmPjESUJsIl6FiHRv Uz9jA/96nxsDQ8YMEr51F3sHubn7BwrYqGOZLT5btLMG1i9OnWyy0npQ5wKvM2bT t2i6QPcHydTAkX+DLXQv8UeJE+Qpq+duoofMpxdFOKgqW3x0kKWGP14UoOqSQFGL K4fStiwR7fCtExrMFKUHaP5Sij7v8VoyBtyK+w45LoWFFXsPeLQhU2NvdHQgRmVu dG9uIDxzajEyZm5AcmFzY2hrZS5uZXQ+iFYEExECABYFAjmoHL8ECwoEAwMVAwID FgIBAheAAAoJEGtrXbm1pSX6WZoAnRzHUYn+/MSVAsmK7bLJrAfmn8Y+AJ4uzZEX OxVuc0sGg/J0AqlYNpMcqrkBDQQ5qBzcEAQAhJgZzAKBjuKwS0owgknuN+5kSu9U tk75ZKRpBMTFfW1Js2E5v96M3Z4XAvyJFhQYaXWZn0QQY4PkrbbfKib4X3Onn/Gx M1mdtWKAXxb1+JuEH/dpVemt2EDLn6b2VVI5iE6U0HcrJjkvt7DLKsvQFRnnqd6M SHdN3XmxhY+VakcAAwUD/iTTv+fpM+Nn2izo7z0BmRu/+GwQgvOF8Qc+8YA6JgaA UUrD7nO3xUpkoK6gr1se2Wu98BFv2GSKRZZF9QljXn2vGNreYRRI9ZhWpKm3zflz uC7lz63QaiZdAPup37yWYXyaAvUvYufORC4hS9mZUgKbbOC+O6xdzkLBerBk/FK+ iEYEGBECAAYFAjmoHNwACgkQa2tdubWlJfqAvQCfWMWnlCab4pUJEvE4gjSFJ+EV 5LsAn2yeJT+7MWYKIQpPmGMMjeGkykK1 =tjOP -----END PGP PUBLIC KEY BLOCK----- |
|
From: Hans B P. <ha...@di...> - 2000-08-30 11:39:25
|
Scott Fenton wrote: > > > mlist.ccc : Complete CCC database sorted by manufacturer and date > > no errors when run throught the parser (below). > > YAHOO!!! 0.5 goes out later today. Tht's great! I was just playing around and put together a little HTML generator. File is html.c at <ftp://aconit.org/pub> take the node.h file also in place of the NODE.H, just a coupleof minor changes necessitated by the first clinet program of parser. Well, I really do have to go now, type with you this weekend.... -- Hans |
|
From: Scott F. <sj...@ra...> - 2000-08-30 11:13:54
|
On Wed, Aug 30, 2000 at 05:51:42AM +0100, the keyboard of Hans B Pufal wrote: > Hello agian, > > I have not had time to figure out my CVS problems. > > I have uploaded to <ftp://aconit.org/pub> some files as follows: > > mlist.ccc : Complete CCC database sorted by manufacturer and date > no errors when run throught the parser (below). YAHOO!!! 0.5 goes out later today. > > parser.c > node.h > syntax3 : New parser files which do more data checking, save > multiple > values for links and strings and more efficiently allocate memory. I > compiled and verified this version on GCC and Mandrake 7.0. > Theyll be in. > > So if one of you could check these in I would appreciate it. > > I will be gone on a business trip for the next three days, don't know if > I will be able to see my eMail or not. > OK, so long. > Regards > > -- Hans B Pufal > _______________________________________________ > Comp-hist-devel mailing list > Com...@li... > http://lists.sourceforge.net/mailman/listinfo/comp-hist-devel -- -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.0.2 (GNU/Linux) Comment: For info see http://www.gnupg.org mQGiBDmoHL8RBACt7yc65iKzR4IW2kKF0wjfZlRVwcwEws6HueM9uKF6HCzyFtyM XJiHz8f3LI2NY/GedfF+XTFc2zQlPummiOrHfAx9Y2hV4ajEpxNgqm36BT21vLuI iTB6roHHm+EiK9dRINyc+kB4v5QV5S9BGxPuygm/3yLZLmGH6RUmSxis1wCgvGnX n3qhbP7Yf/mLO1Du3oEJhR8EAI+TFhyxg3y2xv++xCxKOL9ofF+wPA4EkXPCAokW 10hDmeGY246wOMPWC0Hou1QJqqRN82n5BbJAzUnE/Iht82SEJgM1vhIbp0uShUdS jzKPnBBUTzLQFPbAG9hDaU/98JklsyDIbacavCuCtky6Xs/wmPjESUJsIl6FiHRv Uz9jA/96nxsDQ8YMEr51F3sHubn7BwrYqGOZLT5btLMG1i9OnWyy0npQ5wKvM2bT t2i6QPcHydTAkX+DLXQv8UeJE+Qpq+duoofMpxdFOKgqW3x0kKWGP14UoOqSQFGL K4fStiwR7fCtExrMFKUHaP5Sij7v8VoyBtyK+w45LoWFFXsPeLQhU2NvdHQgRmVu dG9uIDxzajEyZm5AcmFzY2hrZS5uZXQ+iFYEExECABYFAjmoHL8ECwoEAwMVAwID FgIBAheAAAoJEGtrXbm1pSX6WZoAnRzHUYn+/MSVAsmK7bLJrAfmn8Y+AJ4uzZEX OxVuc0sGg/J0AqlYNpMcqrkBDQQ5qBzcEAQAhJgZzAKBjuKwS0owgknuN+5kSu9U tk75ZKRpBMTFfW1Js2E5v96M3Z4XAvyJFhQYaXWZn0QQY4PkrbbfKib4X3Onn/Gx M1mdtWKAXxb1+JuEH/dpVemt2EDLn6b2VVI5iE6U0HcrJjkvt7DLKsvQFRnnqd6M SHdN3XmxhY+VakcAAwUD/iTTv+fpM+Nn2izo7z0BmRu/+GwQgvOF8Qc+8YA6JgaA UUrD7nO3xUpkoK6gr1se2Wu98BFv2GSKRZZF9QljXn2vGNreYRRI9ZhWpKm3zflz uC7lz63QaiZdAPup37yWYXyaAvUvYufORC4hS9mZUgKbbOC+O6xdzkLBerBk/FK+ iEYEGBECAAYFAjmoHNwACgkQa2tdubWlJfqAvQCfWMWnlCab4pUJEvE4gjSFJ+EV 5LsAn2yeJT+7MWYKIQpPmGMMjeGkykK1 =tjOP -----END PGP PUBLIC KEY BLOCK----- |
|
From: Hans B P. <ha...@di...> - 2000-08-30 03:52:20
|
Hello agian, I have not had time to figure out my CVS problems. I have uploaded to <ftp://aconit.org/pub> some files as follows: mlist.ccc : Complete CCC database sorted by manufacturer and date no errors when run throught the parser (below). parser.c node.h syntax3 : New parser files which do more data checking, save multiple values for links and strings and more efficiently allocate memory. I compiled and verified this version on GCC and Mandrake 7.0. So if one of you could check these in I would appreciate it. I will be gone on a business trip for the next three days, don't know if I will be able to see my eMail or not. Regards -- Hans B Pufal |
|
From: Scott F. <sj...@ra...> - 2000-08-29 12:25:36
|
On Tue, Aug 29, 2000 at 02:14:34PM +0100, the keyboard of Hans B Pufal wrote: > Scott Fenton wrote: > > > On Tue, Aug 29, 2000 at 06:13:28AM -0400, the keyboard of Kurt Raschke wrote: > > > Hans brings up a good point - we have the Reference: field, however that may > > >not always be enough. So, what is our policy on use of an existing history pr > > >oject? Do we take what we need and then drop them a note when we're done inco>rporating their project, or do we ask them at the outset, and then go ahead? > > > > To be honest, I don't really know. What I can tell you is that I've taken from three trees (two voluntarily, one because we forked from them). What I've done in each of those cases (except the original, of course) is fork, then drop a polite note. > > Yes but presumably thee were GPL'd. Here we are talking of copyrighted > materiel (at computer history center). On the other hand, it is valid to > use and cite sources fro research, but whre do you draw the line? Plagerism, I guess. > > -- Hans > _______________________________________________ > Comp-hist-devel mailing list > Com...@li... > http://lists.sourceforge.net/mailman/listinfo/comp-hist-devel -- -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.0.2 (GNU/Linux) Comment: For info see http://www.gnupg.org mQGiBDmoHL8RBACt7yc65iKzR4IW2kKF0wjfZlRVwcwEws6HueM9uKF6HCzyFtyM XJiHz8f3LI2NY/GedfF+XTFc2zQlPummiOrHfAx9Y2hV4ajEpxNgqm36BT21vLuI iTB6roHHm+EiK9dRINyc+kB4v5QV5S9BGxPuygm/3yLZLmGH6RUmSxis1wCgvGnX n3qhbP7Yf/mLO1Du3oEJhR8EAI+TFhyxg3y2xv++xCxKOL9ofF+wPA4EkXPCAokW 10hDmeGY246wOMPWC0Hou1QJqqRN82n5BbJAzUnE/Iht82SEJgM1vhIbp0uShUdS jzKPnBBUTzLQFPbAG9hDaU/98JklsyDIbacavCuCtky6Xs/wmPjESUJsIl6FiHRv Uz9jA/96nxsDQ8YMEr51F3sHubn7BwrYqGOZLT5btLMG1i9OnWyy0npQ5wKvM2bT t2i6QPcHydTAkX+DLXQv8UeJE+Qpq+duoofMpxdFOKgqW3x0kKWGP14UoOqSQFGL K4fStiwR7fCtExrMFKUHaP5Sij7v8VoyBtyK+w45LoWFFXsPeLQhU2NvdHQgRmVu dG9uIDxzajEyZm5AcmFzY2hrZS5uZXQ+iFYEExECABYFAjmoHL8ECwoEAwMVAwID FgIBAheAAAoJEGtrXbm1pSX6WZoAnRzHUYn+/MSVAsmK7bLJrAfmn8Y+AJ4uzZEX OxVuc0sGg/J0AqlYNpMcqrkBDQQ5qBzcEAQAhJgZzAKBjuKwS0owgknuN+5kSu9U tk75ZKRpBMTFfW1Js2E5v96M3Z4XAvyJFhQYaXWZn0QQY4PkrbbfKib4X3Onn/Gx M1mdtWKAXxb1+JuEH/dpVemt2EDLn6b2VVI5iE6U0HcrJjkvt7DLKsvQFRnnqd6M SHdN3XmxhY+VakcAAwUD/iTTv+fpM+Nn2izo7z0BmRu/+GwQgvOF8Qc+8YA6JgaA UUrD7nO3xUpkoK6gr1se2Wu98BFv2GSKRZZF9QljXn2vGNreYRRI9ZhWpKm3zflz uC7lz63QaiZdAPup37yWYXyaAvUvYufORC4hS9mZUgKbbOC+O6xdzkLBerBk/FK+ iEYEGBECAAYFAjmoHNwACgkQa2tdubWlJfqAvQCfWMWnlCab4pUJEvE4gjSFJ+EV 5LsAn2yeJT+7MWYKIQpPmGMMjeGkykK1 =tjOP -----END PGP PUBLIC KEY BLOCK----- |
|
From: Hans B P. <ha...@di...> - 2000-08-29 12:15:15
|
Scott Fenton wrote: > On Tue, Aug 29, 2000 at 06:13:28AM -0400, the keyboard of Kurt Raschke wrote: > > Hans brings up a good point - we have the Reference: field, however that may > >not always be enough. So, what is our policy on use of an existing history pr > >oject? Do we take what we need and then drop them a note when we're done inco>rporating their project, or do we ask them at the outset, and then go ahead? > > To be honest, I don't really know. What I can tell you is that I've taken from three trees (two voluntarily, one because we forked from them). What I've done in each of those cases (except the original, of course) is fork, then drop a polite note. Yes but presumably thee were GPL'd. Here we are talking of copyrighted materiel (at computer history center). On the other hand, it is valid to use and cite sources fro research, but whre do you draw the line? -- Hans |
|
From: Scott F. <sj...@ra...> - 2000-08-29 11:51:59
|
On Tue, Aug 29, 2000 at 06:13:28AM -0400, the keyboard of Kurt Raschke wrote: > Hans brings up a good point - we have the Reference: field, however that may >not always be enough. So, what is our policy on use of an existing history pr >oject? Do we take what we need and then drop them a note when we're done inco>rporating their project, or do we ask them at the outset, and then go ahead? To be honest, I don't really know. What I can tell you is that I've taken from three trees (two voluntarily, one because we forked from them). What I've done in each of those cases (except the original, of course) is fork, then drop a polite note. -Scott > > -Kurt > On Tue, Aug 29, 2000 at 07:31:25AM +0100, Hans B Pufal wrote: > > Have you seen his : > > <http://www.computerhistory.org/exhibits/microprocessors/index.page> > > > > Very nice map of microprocessor deveopments, now I want to add > > fileds for transistor count, silicon size and speed !! > > > > I wonder about the ethics of taking that information and incorporating > > it into our database? > > > > Regards > > > > -- Hans B Pufal > > _______________________________________________ > > Comp-hist-devel mailing list > > Com...@li... > > http://lists.sourceforge.net/mailman/listinfo/comp-hist-devel > _______________________________________________ > Comp-hist-devel mailing list > Com...@li... > http://lists.sourceforge.net/mailman/listinfo/comp-hist-devel -- -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.0.2 (GNU/Linux) Comment: For info see http://www.gnupg.org mQGiBDmoHL8RBACt7yc65iKzR4IW2kKF0wjfZlRVwcwEws6HueM9uKF6HCzyFtyM XJiHz8f3LI2NY/GedfF+XTFc2zQlPummiOrHfAx9Y2hV4ajEpxNgqm36BT21vLuI iTB6roHHm+EiK9dRINyc+kB4v5QV5S9BGxPuygm/3yLZLmGH6RUmSxis1wCgvGnX n3qhbP7Yf/mLO1Du3oEJhR8EAI+TFhyxg3y2xv++xCxKOL9ofF+wPA4EkXPCAokW 10hDmeGY246wOMPWC0Hou1QJqqRN82n5BbJAzUnE/Iht82SEJgM1vhIbp0uShUdS jzKPnBBUTzLQFPbAG9hDaU/98JklsyDIbacavCuCtky6Xs/wmPjESUJsIl6FiHRv Uz9jA/96nxsDQ8YMEr51F3sHubn7BwrYqGOZLT5btLMG1i9OnWyy0npQ5wKvM2bT t2i6QPcHydTAkX+DLXQv8UeJE+Qpq+duoofMpxdFOKgqW3x0kKWGP14UoOqSQFGL K4fStiwR7fCtExrMFKUHaP5Sij7v8VoyBtyK+w45LoWFFXsPeLQhU2NvdHQgRmVu dG9uIDxzajEyZm5AcmFzY2hrZS5uZXQ+iFYEExECABYFAjmoHL8ECwoEAwMVAwID FgIBAheAAAoJEGtrXbm1pSX6WZoAnRzHUYn+/MSVAsmK7bLJrAfmn8Y+AJ4uzZEX OxVuc0sGg/J0AqlYNpMcqrkBDQQ5qBzcEAQAhJgZzAKBjuKwS0owgknuN+5kSu9U tk75ZKRpBMTFfW1Js2E5v96M3Z4XAvyJFhQYaXWZn0QQY4PkrbbfKib4X3Onn/Gx M1mdtWKAXxb1+JuEH/dpVemt2EDLn6b2VVI5iE6U0HcrJjkvt7DLKsvQFRnnqd6M SHdN3XmxhY+VakcAAwUD/iTTv+fpM+Nn2izo7z0BmRu/+GwQgvOF8Qc+8YA6JgaA UUrD7nO3xUpkoK6gr1se2Wu98BFv2GSKRZZF9QljXn2vGNreYRRI9ZhWpKm3zflz uC7lz63QaiZdAPup37yWYXyaAvUvYufORC4hS9mZUgKbbOC+O6xdzkLBerBk/FK+ iEYEGBECAAYFAjmoHNwACgkQa2tdubWlJfqAvQCfWMWnlCab4pUJEvE4gjSFJ+EV 5LsAn2yeJT+7MWYKIQpPmGMMjeGkykK1 =tjOP -----END PGP PUBLIC KEY BLOCK----- |
|
From: Kurt R. <ku...@ra...> - 2000-08-29 10:13:37
|
Hans brings up a good point - we have the Reference: field, however that may not always be enough. So, what is our policy on use of an existing history project? Do we take what we need and then drop them a note when we're done incorporating their project, or do we ask them at the outset, and then go ahead? -Kurt On Tue, Aug 29, 2000 at 07:31:25AM +0100, Hans B Pufal wrote: > Have you seen his : > <http://www.computerhistory.org/exhibits/microprocessors/index.page> > > Very nice map of microprocessor deveopments, now I want to add > fileds for transistor count, silicon size and speed !! > > I wonder about the ethics of taking that information and incorporating > it into our database? > > Regards > > -- Hans B Pufal > _______________________________________________ > Comp-hist-devel mailing list > Com...@li... > http://lists.sourceforge.net/mailman/listinfo/comp-hist-devel |
|
From: Hans B P. <ha...@di...> - 2000-08-29 05:31:52
|
Have you seen his : <http://www.computerhistory.org/exhibits/microprocessors/index.page> Very nice map of microprocessor deveopments, now I want to add fileds for transistor count, silicon size and speed !! I wonder about the ethics of taking that information and incorporating it into our database? Regards -- Hans B Pufal |
|
From: Hans B P. <ha...@di...> - 2000-08-29 05:27:08
|
Hi guys, Yes I'm still hear, tring to dig myseld from under the rubble caused by Windows trrashing my primary data disk. The problems were compounded by the fact that I cannot read the backup I made 10 days ago - such is life.... Anyways, I have an updated parser with everything except the multiple field patch that Christophe mentioned - I found the bug he fixed earlier on. I have tried unsuccessfully to get my new Win2K system to run CVS, I'm going to try my Linux box when I get chance. If nayone wants to upload the new parser drop me a line and I'll send it privately or tell me to post it here. On teh CCC front, I found a suitable backup copy on another disk and recreated my master node list and put it through my parser successfully. I would like to check that in as mlist.ccc (or somesuch) as being the masert list from CCC, we can all then hack at it to separate out into manageable files. Again I'll send it to anyone who can check it in. I REALLY must get CVS access..... Reagards, -- Hans B Pufal |
|
From: Johnny F. <chr...@fn...> - 2000-08-28 20:04:57
|
-------------------
>
> > 2. The file sinclair was not correctly parsed because it contains
lines
more
> > than 512 characters long
>
> Ah tht's easy to fix ;-) I am thinking of redoing the input parser
to
eliminate
> all line length restrictions.
>
> > 3. Now, it correctly deals with nodes which have several Successor
to fields
>
> Oooh, did not think of that? How is that handled, where do we keep
the links?
> Presumably should handle multiples of any of the link fields.
Once again, sorry if I didn't post the updated parser.`
I just slightly modified your approach to the links : instead of using
a void
pointer which is used as char * or struct Node *, I created a linked
list of
such void pointers and after fighting with a few segfaults, it worked.
>
> > Now that we have a working C parser, we can easily convert our
database to
> > an sql database and allow people to consult our database using
php.
If you
> > want such an access, I can do it but not before mid september
>
> Indeed...
>
> > Next week, I'll be away so I won't be able to do any work for the
project.
> > At least, I'll try to check my mails regularly.
>
> Have a good holiday (I presume).
Unfortunately, no, I work.
>
> -- Hans
>
> _______________________________________________
> Comp-hist-devel mailing list
> Com...@li...
> http://lists.sourceforge.net/mailman/listinfo/comp-hist-devel
>
|
|
From: Johnny F. <chr...@fn...> - 2000-08-28 19:57:27
|
-------------------
> Kurt Raschke wrote:
>
> > I can't get it to compile:
> > [kurt@linux parser]$ gcc -DTESTING parser.c
> > parser.c: In function `parse_line':
> > parser.c:230: invalid lvalue in unary `&'
>
> Oops, I use the Borland compiler, I really should test it on GCC
before
shipping.
>
> I think this is the same issue that Christophe mentioned in his
eMail,
> unfortunately I don't have a copy of his fixes yet.
>
Didn't I post it with my last message ? If I didn't do it, you'll have
to wait
until sunday... To fix the compilation, I just changed in parse_line
a
&(??? *) with (??? **)& (sorry to be so imprecise... maybe it will be
helpful)
> > Any ideas?
>
> I'm working on it...
>
> --Hans
>
> _______________________________________________
> Comp-hist-devel mailing list
> Com...@li...
> http://lists.sourceforge.net/mailman/listinfo/comp-hist-devel
>
|
|
From: Scott F. <sj...@ra...> - 2000-08-27 16:59:29
|
On Sun, Aug 27, 2000 at 06:27:54PM +0100, the keyboard of Hans B Pufal wrote: > Scott Fenton wrote: > > > OK, I've become sick of all this arguing over the C parser. It is now in CVS. > > Thanks for that Scott, didn't realize we were arguing though! I was just becoming impatient. > > I had a little problem this weekend, MS Windows decided it was time to trash all > my data, it > completely wiped out my data dirive! > > What does this mean? Well it will take a littel time to recover the data. More > importantly I have moved to Windows 2000, hopefully that will be more stable.... > > I got WinCVS and have installed it and am trying to connect to the comp-hist > repository. When I log on with SSH I get a mesage saying "this is a restricted > account, you cannot execute anything here" and it logs me off. > > I assume I do not have the correct CVS server name, I first used > cvs.sourceforge.net then > cvs.comp-hist.sourceforge.net and ot the same results. What is the correct server > name? > cvs.comp-hist.sourceforge.net. Take a look at sfdocs.sourceforge.net for help with CVS. And again, not to be pushy, but how goeth CCC? > Regards > > -- Hans > > > > > > > > > -Scott > > > > -- > > -----BEGIN PGP PUBLIC KEY BLOCK----- > > Version: GnuPG v1.0.2 (GNU/Linux) > > Comment: For info see http://www.gnupg.org > > > > mQGiBDmoHL8RBACt7yc65iKzR4IW2kKF0wjfZlRVwcwEws6HueM9uKF6HCzyFtyM > > XJiHz8f3LI2NY/GedfF+XTFc2zQlPummiOrHfAx9Y2hV4ajEpxNgqm36BT21vLuI > > iTB6roHHm+EiK9dRINyc+kB4v5QV5S9BGxPuygm/3yLZLmGH6RUmSxis1wCgvGnX > > n3qhbP7Yf/mLO1Du3oEJhR8EAI+TFhyxg3y2xv++xCxKOL9ofF+wPA4EkXPCAokW > > 10hDmeGY246wOMPWC0Hou1QJqqRN82n5BbJAzUnE/Iht82SEJgM1vhIbp0uShUdS > > jzKPnBBUTzLQFPbAG9hDaU/98JklsyDIbacavCuCtky6Xs/wmPjESUJsIl6FiHRv > > Uz9jA/96nxsDQ8YMEr51F3sHubn7BwrYqGOZLT5btLMG1i9OnWyy0npQ5wKvM2bT > > t2i6QPcHydTAkX+DLXQv8UeJE+Qpq+duoofMpxdFOKgqW3x0kKWGP14UoOqSQFGL > > K4fStiwR7fCtExrMFKUHaP5Sij7v8VoyBtyK+w45LoWFFXsPeLQhU2NvdHQgRmVu > > dG9uIDxzajEyZm5AcmFzY2hrZS5uZXQ+iFYEExECABYFAjmoHL8ECwoEAwMVAwID > > FgIBAheAAAoJEGtrXbm1pSX6WZoAnRzHUYn+/MSVAsmK7bLJrAfmn8Y+AJ4uzZEX > > OxVuc0sGg/J0AqlYNpMcqrkBDQQ5qBzcEAQAhJgZzAKBjuKwS0owgknuN+5kSu9U > > tk75ZKRpBMTFfW1Js2E5v96M3Z4XAvyJFhQYaXWZn0QQY4PkrbbfKib4X3Onn/Gx > > M1mdtWKAXxb1+JuEH/dpVemt2EDLn6b2VVI5iE6U0HcrJjkvt7DLKsvQFRnnqd6M > > SHdN3XmxhY+VakcAAwUD/iTTv+fpM+Nn2izo7z0BmRu/+GwQgvOF8Qc+8YA6JgaA > > UUrD7nO3xUpkoK6gr1se2Wu98BFv2GSKRZZF9QljXn2vGNreYRRI9ZhWpKm3zflz > > uC7lz63QaiZdAPup37yWYXyaAvUvYufORC4hS9mZUgKbbOC+O6xdzkLBerBk/FK+ > > iEYEGBECAAYFAjmoHNwACgkQa2tdubWlJfqAvQCfWMWnlCab4pUJEvE4gjSFJ+EV > > 5LsAn2yeJT+7MWYKIQpPmGMMjeGkykK1 > > =tjOP > > -----END PGP PUBLIC KEY BLOCK----- > > _______________________________________________ > > Comp-hist-devel mailing list > > Com...@li... > > http://lists.sourceforge.net/mailman/listinfo/comp-hist-devel > > _______________________________________________ > Comp-hist-devel mailing list > Com...@li... > http://lists.sourceforge.net/mailman/listinfo/comp-hist-devel -- -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.0.2 (GNU/Linux) Comment: For info see http://www.gnupg.org mQGiBDmoHL8RBACt7yc65iKzR4IW2kKF0wjfZlRVwcwEws6HueM9uKF6HCzyFtyM XJiHz8f3LI2NY/GedfF+XTFc2zQlPummiOrHfAx9Y2hV4ajEpxNgqm36BT21vLuI iTB6roHHm+EiK9dRINyc+kB4v5QV5S9BGxPuygm/3yLZLmGH6RUmSxis1wCgvGnX n3qhbP7Yf/mLO1Du3oEJhR8EAI+TFhyxg3y2xv++xCxKOL9ofF+wPA4EkXPCAokW 10hDmeGY246wOMPWC0Hou1QJqqRN82n5BbJAzUnE/Iht82SEJgM1vhIbp0uShUdS jzKPnBBUTzLQFPbAG9hDaU/98JklsyDIbacavCuCtky6Xs/wmPjESUJsIl6FiHRv Uz9jA/96nxsDQ8YMEr51F3sHubn7BwrYqGOZLT5btLMG1i9OnWyy0npQ5wKvM2bT t2i6QPcHydTAkX+DLXQv8UeJE+Qpq+duoofMpxdFOKgqW3x0kKWGP14UoOqSQFGL K4fStiwR7fCtExrMFKUHaP5Sij7v8VoyBtyK+w45LoWFFXsPeLQhU2NvdHQgRmVu dG9uIDxzajEyZm5AcmFzY2hrZS5uZXQ+iFYEExECABYFAjmoHL8ECwoEAwMVAwID FgIBAheAAAoJEGtrXbm1pSX6WZoAnRzHUYn+/MSVAsmK7bLJrAfmn8Y+AJ4uzZEX OxVuc0sGg/J0AqlYNpMcqrkBDQQ5qBzcEAQAhJgZzAKBjuKwS0owgknuN+5kSu9U tk75ZKRpBMTFfW1Js2E5v96M3Z4XAvyJFhQYaXWZn0QQY4PkrbbfKib4X3Onn/Gx M1mdtWKAXxb1+JuEH/dpVemt2EDLn6b2VVI5iE6U0HcrJjkvt7DLKsvQFRnnqd6M SHdN3XmxhY+VakcAAwUD/iTTv+fpM+Nn2izo7z0BmRu/+GwQgvOF8Qc+8YA6JgaA UUrD7nO3xUpkoK6gr1se2Wu98BFv2GSKRZZF9QljXn2vGNreYRRI9ZhWpKm3zflz uC7lz63QaiZdAPup37yWYXyaAvUvYufORC4hS9mZUgKbbOC+O6xdzkLBerBk/FK+ iEYEGBECAAYFAjmoHNwACgkQa2tdubWlJfqAvQCfWMWnlCab4pUJEvE4gjSFJ+EV 5LsAn2yeJT+7MWYKIQpPmGMMjeGkykK1 =tjOP -----END PGP PUBLIC KEY BLOCK----- |
|
From: Hans B P. <ha...@di...> - 2000-08-27 16:28:11
|
Scott Fenton wrote: > OK, I've become sick of all this arguing over the C parser. It is now in CVS. Thanks for that Scott, didn't realize we were arguing though! I had a little problem this weekend, MS Windows decided it was time to trash all my data, it completely wiped out my data dirive! What does this mean? Well it will take a littel time to recover the data. More importantly I have moved to Windows 2000, hopefully that will be more stable.... I got WinCVS and have installed it and am trying to connect to the comp-hist repository. When I log on with SSH I get a mesage saying "this is a restricted account, you cannot execute anything here" and it logs me off. I assume I do not have the correct CVS server name, I first used cvs.sourceforge.net then cvs.comp-hist.sourceforge.net and ot the same results. What is the correct server name? Regards -- Hans > > > -Scott > > -- > -----BEGIN PGP PUBLIC KEY BLOCK----- > Version: GnuPG v1.0.2 (GNU/Linux) > Comment: For info see http://www.gnupg.org > > mQGiBDmoHL8RBACt7yc65iKzR4IW2kKF0wjfZlRVwcwEws6HueM9uKF6HCzyFtyM > XJiHz8f3LI2NY/GedfF+XTFc2zQlPummiOrHfAx9Y2hV4ajEpxNgqm36BT21vLuI > iTB6roHHm+EiK9dRINyc+kB4v5QV5S9BGxPuygm/3yLZLmGH6RUmSxis1wCgvGnX > n3qhbP7Yf/mLO1Du3oEJhR8EAI+TFhyxg3y2xv++xCxKOL9ofF+wPA4EkXPCAokW > 10hDmeGY246wOMPWC0Hou1QJqqRN82n5BbJAzUnE/Iht82SEJgM1vhIbp0uShUdS > jzKPnBBUTzLQFPbAG9hDaU/98JklsyDIbacavCuCtky6Xs/wmPjESUJsIl6FiHRv > Uz9jA/96nxsDQ8YMEr51F3sHubn7BwrYqGOZLT5btLMG1i9OnWyy0npQ5wKvM2bT > t2i6QPcHydTAkX+DLXQv8UeJE+Qpq+duoofMpxdFOKgqW3x0kKWGP14UoOqSQFGL > K4fStiwR7fCtExrMFKUHaP5Sij7v8VoyBtyK+w45LoWFFXsPeLQhU2NvdHQgRmVu > dG9uIDxzajEyZm5AcmFzY2hrZS5uZXQ+iFYEExECABYFAjmoHL8ECwoEAwMVAwID > FgIBAheAAAoJEGtrXbm1pSX6WZoAnRzHUYn+/MSVAsmK7bLJrAfmn8Y+AJ4uzZEX > OxVuc0sGg/J0AqlYNpMcqrkBDQQ5qBzcEAQAhJgZzAKBjuKwS0owgknuN+5kSu9U > tk75ZKRpBMTFfW1Js2E5v96M3Z4XAvyJFhQYaXWZn0QQY4PkrbbfKib4X3Onn/Gx > M1mdtWKAXxb1+JuEH/dpVemt2EDLn6b2VVI5iE6U0HcrJjkvt7DLKsvQFRnnqd6M > SHdN3XmxhY+VakcAAwUD/iTTv+fpM+Nn2izo7z0BmRu/+GwQgvOF8Qc+8YA6JgaA > UUrD7nO3xUpkoK6gr1se2Wu98BFv2GSKRZZF9QljXn2vGNreYRRI9ZhWpKm3zflz > uC7lz63QaiZdAPup37yWYXyaAvUvYufORC4hS9mZUgKbbOC+O6xdzkLBerBk/FK+ > iEYEGBECAAYFAjmoHNwACgkQa2tdubWlJfqAvQCfWMWnlCab4pUJEvE4gjSFJ+EV > 5LsAn2yeJT+7MWYKIQpPmGMMjeGkykK1 > =tjOP > -----END PGP PUBLIC KEY BLOCK----- > _______________________________________________ > Comp-hist-devel mailing list > Com...@li... > http://lists.sourceforge.net/mailman/listinfo/comp-hist-devel |
|
From: Scott F. <sj...@ra...> - 2000-08-27 14:39:17
|
OK, I've become sick of all this arguing over the C parser. It is now in CVS. -Scott -- -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.0.2 (GNU/Linux) Comment: For info see http://www.gnupg.org mQGiBDmoHL8RBACt7yc65iKzR4IW2kKF0wjfZlRVwcwEws6HueM9uKF6HCzyFtyM XJiHz8f3LI2NY/GedfF+XTFc2zQlPummiOrHfAx9Y2hV4ajEpxNgqm36BT21vLuI iTB6roHHm+EiK9dRINyc+kB4v5QV5S9BGxPuygm/3yLZLmGH6RUmSxis1wCgvGnX n3qhbP7Yf/mLO1Du3oEJhR8EAI+TFhyxg3y2xv++xCxKOL9ofF+wPA4EkXPCAokW 10hDmeGY246wOMPWC0Hou1QJqqRN82n5BbJAzUnE/Iht82SEJgM1vhIbp0uShUdS jzKPnBBUTzLQFPbAG9hDaU/98JklsyDIbacavCuCtky6Xs/wmPjESUJsIl6FiHRv Uz9jA/96nxsDQ8YMEr51F3sHubn7BwrYqGOZLT5btLMG1i9OnWyy0npQ5wKvM2bT t2i6QPcHydTAkX+DLXQv8UeJE+Qpq+duoofMpxdFOKgqW3x0kKWGP14UoOqSQFGL K4fStiwR7fCtExrMFKUHaP5Sij7v8VoyBtyK+w45LoWFFXsPeLQhU2NvdHQgRmVu dG9uIDxzajEyZm5AcmFzY2hrZS5uZXQ+iFYEExECABYFAjmoHL8ECwoEAwMVAwID FgIBAheAAAoJEGtrXbm1pSX6WZoAnRzHUYn+/MSVAsmK7bLJrAfmn8Y+AJ4uzZEX OxVuc0sGg/J0AqlYNpMcqrkBDQQ5qBzcEAQAhJgZzAKBjuKwS0owgknuN+5kSu9U tk75ZKRpBMTFfW1Js2E5v96M3Z4XAvyJFhQYaXWZn0QQY4PkrbbfKib4X3Onn/Gx M1mdtWKAXxb1+JuEH/dpVemt2EDLn6b2VVI5iE6U0HcrJjkvt7DLKsvQFRnnqd6M SHdN3XmxhY+VakcAAwUD/iTTv+fpM+Nn2izo7z0BmRu/+GwQgvOF8Qc+8YA6JgaA UUrD7nO3xUpkoK6gr1se2Wu98BFv2GSKRZZF9QljXn2vGNreYRRI9ZhWpKm3zflz uC7lz63QaiZdAPup37yWYXyaAvUvYufORC4hS9mZUgKbbOC+O6xdzkLBerBk/FK+ iEYEGBECAAYFAjmoHNwACgkQa2tdubWlJfqAvQCfWMWnlCab4pUJEvE4gjSFJ+EV 5LsAn2yeJT+7MWYKIQpPmGMMjeGkykK1 =tjOP -----END PGP PUBLIC KEY BLOCK----- |
|
From: Scott F. <sj...@ra...> - 2000-08-27 04:40:46
|
On Sun, Aug 27, 2000 at 06:31:06AM +0200, the keyboard of Hans B Pufal wrote: > Christophe Fergeau wrote: > > > I fixed a few things in the parser : > > > > 1. On my machine, it could not compile (type casting pb in parse_line) > > Sorry about that. I do use a Borland compiler, should set it to strict ANSI I > suppose. Is this the same problme Kurt has with version 3? Can you send me a > copy so I can fix mine? > > > 2. The file sinclair was not correctly parsed because it contains lines more > > than 512 characters long > > Ah tht's easy to fix ;-) I am thinking of redoing the input parser to eliminate > all line length restrictions. > > > 3. Now, it correctly deals with nodes which have several Successor to fields > > Oooh, did not think of that? How is that handled, where do we keep the links? > Presumably should handle multiples of any of the link fields. > > > Now that we have a working C parser, we can easily convert our database to > > an sql database and allow people to consult our database using php. If you > > want such an access, I can do it but not before mid september > > Indeed... I've also been working out (in my head) a way for DBM databases to work, so Perl will have an easy time accessing them. Any ideas? > > > Next week, I'll be away so I won't be able to do any work for the project. > > At least, I'll try to check my mails regularly. > > Have a good holiday (I presume). > > -- Hans > > _______________________________________________ > Comp-hist-devel mailing list > Com...@li... > http://lists.sourceforge.net/mailman/listinfo/comp-hist-devel Overall, my current advice is to get it checked into CVS, after that we can deal with problems in a more graceful manner. Oh, and not to nag, but what's the status of CCC? -- -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.0.2 (GNU/Linux) Comment: For info see http://www.gnupg.org mQGiBDmoHL8RBACt7yc65iKzR4IW2kKF0wjfZlRVwcwEws6HueM9uKF6HCzyFtyM XJiHz8f3LI2NY/GedfF+XTFc2zQlPummiOrHfAx9Y2hV4ajEpxNgqm36BT21vLuI iTB6roHHm+EiK9dRINyc+kB4v5QV5S9BGxPuygm/3yLZLmGH6RUmSxis1wCgvGnX n3qhbP7Yf/mLO1Du3oEJhR8EAI+TFhyxg3y2xv++xCxKOL9ofF+wPA4EkXPCAokW 10hDmeGY246wOMPWC0Hou1QJqqRN82n5BbJAzUnE/Iht82SEJgM1vhIbp0uShUdS jzKPnBBUTzLQFPbAG9hDaU/98JklsyDIbacavCuCtky6Xs/wmPjESUJsIl6FiHRv Uz9jA/96nxsDQ8YMEr51F3sHubn7BwrYqGOZLT5btLMG1i9OnWyy0npQ5wKvM2bT t2i6QPcHydTAkX+DLXQv8UeJE+Qpq+duoofMpxdFOKgqW3x0kKWGP14UoOqSQFGL K4fStiwR7fCtExrMFKUHaP5Sij7v8VoyBtyK+w45LoWFFXsPeLQhU2NvdHQgRmVu dG9uIDxzajEyZm5AcmFzY2hrZS5uZXQ+iFYEExECABYFAjmoHL8ECwoEAwMVAwID FgIBAheAAAoJEGtrXbm1pSX6WZoAnRzHUYn+/MSVAsmK7bLJrAfmn8Y+AJ4uzZEX OxVuc0sGg/J0AqlYNpMcqrkBDQQ5qBzcEAQAhJgZzAKBjuKwS0owgknuN+5kSu9U tk75ZKRpBMTFfW1Js2E5v96M3Z4XAvyJFhQYaXWZn0QQY4PkrbbfKib4X3Onn/Gx M1mdtWKAXxb1+JuEH/dpVemt2EDLn6b2VVI5iE6U0HcrJjkvt7DLKsvQFRnnqd6M SHdN3XmxhY+VakcAAwUD/iTTv+fpM+Nn2izo7z0BmRu/+GwQgvOF8Qc+8YA6JgaA UUrD7nO3xUpkoK6gr1se2Wu98BFv2GSKRZZF9QljXn2vGNreYRRI9ZhWpKm3zflz uC7lz63QaiZdAPup37yWYXyaAvUvYufORC4hS9mZUgKbbOC+O6xdzkLBerBk/FK+ iEYEGBECAAYFAjmoHNwACgkQa2tdubWlJfqAvQCfWMWnlCab4pUJEvE4gjSFJ+EV 5LsAn2yeJT+7MWYKIQpPmGMMjeGkykK1 =tjOP -----END PGP PUBLIC KEY BLOCK----- |
|
From: Hans B P. <ha...@di...> - 2000-08-27 04:35:48
|
Christophe Fergeau wrote: > Well now, thanks to Hans, it is functional, easily extensible and can be > easily integrated in other programs so I think it should be in cvs. Yes... -- Hans |
|
From: Hans B P. <ha...@di...> - 2000-08-27 04:35:08
|
Kurt Raschke wrote: > I can't get it to compile: > [kurt@linux parser]$ gcc -DTESTING parser.c > parser.c: In function `parse_line': > parser.c:230: invalid lvalue in unary `&' Oops, I use the Borland compiler, I really should test it on GCC before shipping. I think this is the same issue that Christophe mentioned in his eMail, unfortunately I don't have a copy of his fixes yet. > Any ideas? I'm working on it... --Hans |
|
From: Hans B P. <ha...@di...> - 2000-08-27 04:33:35
|
Christophe Fergeau wrote: > I fixed a few things in the parser : > > 1. On my machine, it could not compile (type casting pb in parse_line) Sorry about that. I do use a Borland compiler, should set it to strict ANSI I suppose. Is this the same problme Kurt has with version 3? Can you send me a copy so I can fix mine? > 2. The file sinclair was not correctly parsed because it contains lines more > than 512 characters long Ah tht's easy to fix ;-) I am thinking of redoing the input parser to eliminate all line length restrictions. > 3. Now, it correctly deals with nodes which have several Successor to fields Oooh, did not think of that? How is that handled, where do we keep the links? Presumably should handle multiples of any of the link fields. > Now that we have a working C parser, we can easily convert our database to > an sql database and allow people to consult our database using php. If you > want such an access, I can do it but not before mid september Indeed... > Next week, I'll be away so I won't be able to do any work for the project. > At least, I'll try to check my mails regularly. Have a good holiday (I presume). -- Hans |
|
From: Christophe F. <Chr...@fn...> - 2000-08-26 21:34:59
|
Well now, thanks to Hans, it is functional, easily extensible and can be easily integrated in other programs so I think it should be in cvs. ----- Original Message ----- From: Kurt Raschke <ku...@ra...> To: <com...@li...> Sent: Saturday, August 26, 2000 11:29 PM Subject: Re: [Comp-hist-devel] Updated (again) Parser > Should this be put in CVS? > -Kurt > > > From: "Christophe Fergeau" <Chr...@fn...> > > Reply-To: com...@li... > > Date: Sat, 26 Aug 2000 23:15:07 +0200 > > To: <com...@li...> > > Subject: Re: [Comp-hist-devel] Updated (again) Parser > > > > I fixed a few things in the parser : > > > > 1. On my machine, it could not compile (type casting pb in parse_line) > > 2. The file sinclair was not correctly parsed because it contains lines more > > than 512 characters long > > 3. Now, it correctly deals with nodes which have several Successor to fields > > > > Now that we have a working C parser, we can easily convert our database to > > an sql database and allow people to consult our database using php. If you > > want such an access, I can do it but not before mid september > > > > Next week, I'll be away so I won't be able to do any work for the project. > > At least, I'll try to check my mails regularly. > > > > Chris > > > > ----- Original Message ----- > > From: Hans B Pufal <ha...@di...> > > To: <com...@li...> > > Sent: Saturday, August 26, 2000 9:56 AM > > Subject: [Comp-hist-devel] Updated (again) Parser > > > > > >> OK, I updated the parser again! > >> > >> It is now a module which can be easily integrated into a larger program. > >> > >> The parser code is also independent of the node structure (little bit of > >> tricky coding there!) > >> The node structure is defined in node.h and the preser gets its info > >> from there. So adding a new field is simply a matter of editing two > >> tables in node.h and recompiling. > >> > >> I removed identifiers.* (moved the one required routine to parser.c) and > >> keywords, that data > >> is now in node.h > >> > >> Compiling parser.c alone will generate an obj module ready to be linked, > >> compiling with a define of TESTING will create program which parses all > >> its input files and prints out the > >> nodes read. > >> > >> -- Hans > > > > > > > > > > _______________________________________________ > Comp-hist-devel mailing list > Com...@li... > http://lists.sourceforge.net/mailman/listinfo/comp-hist-devel |
|
From: Kurt R. <ku...@ra...> - 2000-08-26 21:29:05
|
Should this be put in CVS? -Kurt > From: "Christophe Fergeau" <Chr...@fn...> > Reply-To: com...@li... > Date: Sat, 26 Aug 2000 23:15:07 +0200 > To: <com...@li...> > Subject: Re: [Comp-hist-devel] Updated (again) Parser > > I fixed a few things in the parser : > > 1. On my machine, it could not compile (type casting pb in parse_line) > 2. The file sinclair was not correctly parsed because it contains lines more > than 512 characters long > 3. Now, it correctly deals with nodes which have several Successor to fields > > Now that we have a working C parser, we can easily convert our database to > an sql database and allow people to consult our database using php. If you > want such an access, I can do it but not before mid september > > Next week, I'll be away so I won't be able to do any work for the project. > At least, I'll try to check my mails regularly. > > Chris > > ----- Original Message ----- > From: Hans B Pufal <ha...@di...> > To: <com...@li...> > Sent: Saturday, August 26, 2000 9:56 AM > Subject: [Comp-hist-devel] Updated (again) Parser > > >> OK, I updated the parser again! >> >> It is now a module which can be easily integrated into a larger program. >> >> The parser code is also independent of the node structure (little bit of >> tricky coding there!) >> The node structure is defined in node.h and the preser gets its info >> from there. So adding a new field is simply a matter of editing two >> tables in node.h and recompiling. >> >> I removed identifiers.* (moved the one required routine to parser.c) and >> keywords, that data >> is now in node.h >> >> Compiling parser.c alone will generate an obj module ready to be linked, >> compiling with a define of TESTING will create program which parses all >> its input files and prints out the >> nodes read. >> >> -- Hans > > > > |
929 messages has been excluded from this view by a project administrator.
