Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c > #5881 > unrolled thread
| Started by | Uno <Uno@example.invalid> |
|---|---|
| First post | 2011-06-12 00:06 -0600 |
| Last post | 2011-06-16 18:32 +0100 |
| Articles | 11 on this page of 51 — 19 participants |
Back to article view | Back to comp.lang.c
looking at binary files with C Uno <Uno@example.invalid> - 2011-06-12 00:06 -0600
Re: looking at binary files with C Ian Collins <ian-news@hotmail.com> - 2011-06-12 18:41 +1200
Re: looking at binary files with C Uno <Uno@example.invalid> - 2011-06-12 00:58 -0600
Re: looking at binary files with C Barry Schwarz <schwarz45@yahoo.com> - 2011-06-12 00:05 -0700
Re: looking at binary files with C Uno <Uno@example.invalid> - 2011-06-12 01:41 -0600
Re: looking at binary files with C "Joachim Schmitz" <jojo.nospam@schmitz-digital.de> - 2011-06-12 11:44 +0200
Re: looking at binary files with C Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2011-06-12 10:25 -0600
Re: looking at binary files with C Ike Naar <ike@sverige.freeshell.org> - 2011-06-12 10:26 +0000
Re: looking at binary files with C Eric Sosman <esosman@ieee-dot-org.invalid> - 2011-06-12 08:23 -0400
Re: looking at binary files with C Hans Vlems <hvlems@freenet.de> - 2011-06-13 23:48 -0700
Re: looking at binary files with C Tim Rentsch <txr@alumni.caltech.edu> - 2011-06-23 00:55 -0700
Re: looking at binary files with C "BartC" <bc@freeuk.com> - 2011-06-12 14:26 +0100
Re: looking at binary files with C Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2011-06-12 10:24 -0600
Re: looking at binary files with C Uno <Uno@example.invalid> - 2011-06-12 14:47 -0600
Re: looking at binary files with C "BartC" <bc@freeuk.com> - 2011-06-12 22:23 +0100
Re: looking at binary files with C Keith Thompson <kst-u@mib.org> - 2011-06-12 14:29 -0700
Re: looking at binary files with C Uno <Uno@example.invalid> - 2011-06-12 16:31 -0600
Re: looking at binary files with C Keith Thompson <kst-u@mib.org> - 2011-06-12 16:14 -0700
Re: looking at binary files with C Uno <Uno@example.invalid> - 2011-06-12 18:41 -0600
Re: looking at binary files with C Eric Sosman <esosman@ieee-dot-org.invalid> - 2011-06-12 17:42 -0400
Re: looking at binary files with C Uno <Uno@example.invalid> - 2011-06-12 17:01 -0600
Re: looking at binary files with C Keith Thompson <kst-u@mib.org> - 2011-06-12 16:23 -0700
Re: looking at binary files with C Uno <Uno@example.invalid> - 2011-06-12 17:24 -0600
Re: looking at binary files with C Ian Collins <ian-news@hotmail.com> - 2011-06-13 11:28 +1200
Re: looking at binary files with C Geoff <geoff@invalid.invalid> - 2011-06-12 16:52 -0700
Re: looking at binary files with C Keith Thompson <kst-u@mib.org> - 2011-06-13 08:51 -0700
Re: looking at binary files with C Seebs <usenet-nospam@seebs.net> - 2011-06-13 14:39 +0000
Re: looking at binary files with C Uno <Uno@example.invalid> - 2011-06-13 20:01 -0600
Re: looking at binary files with C Keith Thompson <kst-u@mib.org> - 2011-06-13 19:24 -0700
Re: looking at binary files with C Seebs <usenet-nospam@seebs.net> - 2011-06-14 17:02 +0000
Re: looking at binary files with C Uno <Uno@example.invalid> - 2011-06-16 01:32 -0600
Re: looking at binary files with C Eric Sosman <esosman@ieee-dot-org.invalid> - 2011-06-13 07:57 -0400
Re: looking at binary files with C Uno <Uno@example.invalid> - 2011-06-13 20:23 -0600
Re: looking at binary files with C Eric Sosman <esosman@ieee-dot-org.invalid> - 2011-06-13 23:12 -0400
Re: looking at binary files with C lovecreatesbeauty <lovecreatesbeauty@gmail.com> - 2011-06-14 01:09 -0700
Re: looking at binary files with C Oliver Jackson <chexmofo@hotmail.com> - 2011-06-15 20:15 -0700
Re: looking at binary files with C Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2011-06-12 18:41 -0600
Re: looking at binary files with C James Waldby <not@valid.invalid> - 2011-06-13 01:16 +0000
Re: looking at binary files with C Uno <Uno@example.invalid> - 2011-06-12 19:48 -0600
Re: looking at binary files with C "io_x" <a@b.c.invalid> - 2011-06-14 12:19 +0200
Re: looking at binary files with C lovecreatesbeauty <lovecreatesbeauty@gmail.com> - 2011-06-14 03:58 -0700
Re: looking at binary files with C "io_x" <a@b.c.invalid> - 2011-06-14 19:07 +0200
Re: looking at binary files with C "io_x" <a@b.c.invalid> - 2011-06-14 19:46 +0200
Re: looking at binary files with C Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2011-06-14 16:08 -0600
Re: looking at binary files with C Ian Collins <ian-news@hotmail.com> - 2011-06-15 08:47 +1200
Re: looking at binary files with C Hans Vlems <hvlems@freenet.de> - 2011-06-13 23:51 -0700
Re: looking at binary files with C Michael Press <rubrum@pacbell.net> - 2011-06-15 13:06 -0700
Re: looking at binary files with C Uno <Uno@example.invalid> - 2011-06-16 01:38 -0600
Re: looking at binary files with C Michael Press <rubrum@pacbell.net> - 2011-06-16 00:54 -0700
Re: looking at binary files with C James Waldby <not@valid.invalid> - 2011-06-16 16:59 +0000
Re: looking at binary files with C "J. J. Farrell" <jjf@bcs.org.uk> - 2011-06-16 18:32 +0100
Page 3 of 3 — ← Prev page 1 2 [3]
| From | lovecreatesbeauty <lovecreatesbeauty@gmail.com> |
|---|---|
| Date | 2011-06-14 03:58 -0700 |
| Message-ID | <203fd31e-5f12-4919-b9c3-5f8be907e3bd@h12g2000pro.googlegroups.com> |
| In reply to | #6053 |
On Jun 14, 6:19 pm, "io_x" <a...@b.c.invalid> wrote:
> {if(i=='\t')
> P("[\\t, %u]", nc[i]);
> else if(i=='\a')
> P("[\\a, %u]", nc[i]);
> else if(i=='\r')
> P("[\\r, %u]", nc[i]);
> else if(i=='\n')
> P("[\\n, %u]", nc[i]);
> else if(i=='\b')
> P("[\\b, %u]", nc[i]);
> else if(i=='\f')
> P("[\\f, %u]", nc[i]);
> else if(i=='\v')
> P("[\\v, %u]", nc[i]);
> else if(i=='\\')
> P("[\\, %u]", nc[i]);
> else P("[%c, %u]", i, nc[i]);
i think there're some other chars can't be printed. see the demo of
your code. Note the last "PuTTY" brought by running your code.
$ make && ./a.out ./intro.wmv
[cut]
N. Bytes File ./a.out=665107
$ PuTTY
[toc] | [prev] | [next] | [standalone]
| From | "io_x" <a@b.c.invalid> |
|---|---|
| Date | 2011-06-14 19:07 +0200 |
| Message-ID | <4df794e8$0$45734$4fafbaef@reader2.news.tin.it> |
| In reply to | #6054 |
"lovecreatesbeauty" <lovecreatesbeauty@gmail.com> ha scritto nel messaggio
news:203fd31e-5f12-4919-b9c3-5f8be907e3bd@h12g2000pro.googlegroups.com...
>On Jun 14, 6:19 pm, "io_x" <a...@b.c.invalid> wrote:
>> {if(i=='\t')
>> P("[\\t, %u]", nc[i]);
>> else if(i=='\a')
>> P("[\\a, %u]", nc[i]);
>> else if(i=='\r')
>> P("[\\r, %u]", nc[i]);
>> else if(i=='\n')
>> P("[\\n, %u]", nc[i]);
>> else if(i=='\b')
>> P("[\\b, %u]", nc[i]);
>> else if(i=='\f')
>> P("[\\f, %u]", nc[i]);
>> else if(i=='\v')
>> P("[\\v, %u]", nc[i]);
>> else if(i=='\\')
>> P("[\\, %u]", nc[i]);
>> else P("[%c, %u]", i, nc[i]);
>i think there're some other chars can't be printed. see the demo of
>your code. Note the last "PuTTY" brought by running your code.
>
>$ make && ./a.out ./intro.wmv
>
>[cut]
>N. Bytes File ./a.out=665107
>$ PuTTY
i hope it not changed something on your tty...
what about this?
-------------
#include <stdio.h>
#include <stdint.h>
#include <limits.h>
#include <ctype.h>
// macro for types
#define u64 uint64_t
#define u32 uint32_t
#define u16 uint16_t
#define u8 uint8_t
// macro for function
#define P printf
// macro for keyWords
#define G goto
#define R return
#define W while
#define F for
int main(int c, char** a)
{u32 nc[256], i, cont, r;
FILE *pf;
if(sizeof(u32)!=sizeof(int)||CHAR_BIT!=8)
{P("Incompatible with your sys\n"); R 0;}
// P("c=%d s=[%s]\n", c, (a[0]==0?"NULL": a[0]));
if(c<=1) {P("Uso: \">program.exe nomeFile\" \n"); R 0;}
pf=fopen(a[1], "rb");
if(pf==0){P("ERRORE: Non riesco a aprire il file\n"); R 0;}
F(i=0; i<256; ++i)
nc[i]=0;
W(1){i=fgetc(pf);
if(i==(u32)-1||i>=256)
break;
++nc[i];
}
if((i!=(u32)-1&&i>=256)||ferror(pf))
{fclose(pf);
err: P("Some error in read the file\n"); R 0;}
fclose(pf);
F(i=0, cont=0; i<256; ++i)
{r=cont;
cont+=nc[i];
if(cont<r) G err;
}
F(i=0; i<256; ++i)
{if(i=='\t')
P("[%3u,\\t, %5u]",i, nc[i]);
else if(i=='\a')
P("[%3u,\\a, %5u]", i, nc[i]);
else if(i=='\r')
P("[%3u,\\r, %5u]", i, nc[i]);
else if(i=='\n')
P("[%3u,\\n, %5u]", i, nc[i]);
else if(i=='\b')
P("[%3u,\\b, %5u]", i, nc[i]);
else if(i=='\f')
P("[%3u,\\f, %5u]", i, nc[i]);
else if(i=='\v')
P("[%3u,\\v, %5u]", i, nc[i]);
else if(i=='\\')
P("[%3u, \\, %5u]", i, nc[i]);
else if(!isprint(i))
P("[%3u, ?, %5u]", i, nc[i]);
else P("[%3u, %c, %5u]", i, i, nc[i]);
if((i+1)%5==0) P("\n");
}
P("\nN. Bytes File %s=%u\n", (a[1]==0?" ": a[1]), cont);
R 0;
}
-------------
[ 0, ?, 1248][ 1, ?, 1333][ 2, ?, 1429][ 3, ?, 1369][ 4, ?, 1276]
[ 5, ?, 1343][ 6, ?, 1413][ 7,\a, 1405][ 8,\b, 1367][ 9,\t, 1290]
[ 10,\n, 30524][ 11,\v, 1391][ 12,\f, 1313][ 13,\r, 1332][ 14, ?, 1444]
[ 15, ?, 1466][ 16, ?, 1435][ 17, ?, 1348][ 18, ?, 1405][ 19, ?, 1344]
[ 20, ?, 1424][ 21, ?, 1255][ 22, ?, 1473][ 23, ?, 1394][ 24, ?, 1435]
[ 25, ?, 1291][ 26, ?, 1424][ 27, ?, 1312][ 28, ?, 1448][ 29, ?, 1277]
[ 30, ?, 1417][ 31, ?, 1333][ 32, , 58554][ 33, !, 1253][ 34, ", 1279]
[ 35, #, 1298][ 36, $, 1403][ 37, %, 1371][ 38, &, 1350][ 39, ', 1290]
[ 40, (, 2050][ 41, ), 1851][ 42, *, 1316][ 43, +, 1326][ 44, ,, 1619]
[ 45, -, 3583][ 46, ., 15008][ 47, /, 27925][ 48, 0, 60635][ 49, 1, 17627]
[ 50, 2, 17869][ 51, 3, 14044][ 52, 4, 16861][ 53, 5, 16944][ 54, 6, 11511]
[ 55, 7, 10704][ 56, 8, 11907][ 57, 9, 10207][ 58, :, 1763][ 59, ;, 1418]
[ 60, <, 8730][ 61, =, 1349][ 62, >, 8598][ 63, ?, 1313][ 64, @, 1343]
[ 65, A, 3910][ 66, B, 5000][ 67, C, 1925][ 68, D, 4814][ 69, E, 1634]
[ 70, F, 2642][ 71, G, 1399][ 72, H, 1363][ 73, I, 1726][ 74, J, 1397]
[ 75, K, 1293][ 76, L, 3943][ 77, M, 1906][ 78, N, 2002][ 79, O, 1534]
[ 80, P, 3911][ 81, Q, 1513][ 82, R, 11581][ 83, S, 4410][ 84, T, 4797]
[ 85, U, 1573][ 86, V, 1529][ 87, W, 1499][ 88, X, 2159][ 89, Y, 2299]
[ 90, Z, 2124][ 91, [, 7089][ 92, \, 1330][ 93, ], 7118][ 94, ^, 1364]
[ 95, _, 1283][ 96, `, 1366][ 97, a, 4532][ 98, b, 10837][ 99, c, 6712]
[100, d, 8329][101, e, 26005][102, f, 1544][103, g, 2151][104, h, 1766]
[105, i, 7824][106, j, 8641][107, k, 3631][108, l, 4565][109, m, 2140]
[110, n, 21112][111, o, 17556][112, p, 6279][113, q, 1413][114, r, 9049]
[115, s, 7995][116, t, 18286][117, u, 4923][118, v, 2021][119, w, 1432]
[120, x, 2629][121, y, 6059][122, z, 1356][123, {, 1455][124, |, 1331]
[125, }, 1492][126, ~, 1253][127, ?, 1166][128, ?, 1312][129, ?, 1304]
[130, ?, 1345][131, ?, 1358][132, ?, 1309][133, ?, 1245][134, ?, 1331]
[135, ?, 1445][136, ?, 1371][137, ?, 1318][138, ?, 1333][139, ?, 1387]
[140, ?, 1302][141, ?, 1348][142, ?, 1305][143, ?, 1374][144, ?, 1320]
[145, ?, 1304][146, ?, 1350][147, ?, 1359][148, ?, 1466][149, ?, 1320]
[150, ?, 1403][151, ?, 1274][152, ?, 1363][153, ?, 1383][154, ?, 1375]
[155, ?, 1335][156, ?, 1597][157, ?, 1274][158, ?, 1480][159, ?, 1295]
[160, ?, 1286][161, ?, 1366][162, ?, 1375][163, ?, 1415][164, ?, 1274]
[165, ?, 1252][166, ?, 1369][167, ?, 1315][168, ?, 1343][169, ?, 1333]
[170, ?, 1467][171, ?, 1492][172, ?, 1325][173, ?, 1352][174, ?, 1423]
[175, ?, 1363][176, ?, 1285][177, ?, 1379][178, ?, 1525][179, ?, 1369]
[180, ?, 1255][181, ?, 1385][182, ?, 1481][183, ?, 1333][184, ?, 1265]
[185, ?, 1301][186, ?, 1443][187, ?, 1412][188, ?, 1254][189, ?, 1359]
[190, ?, 1405][191, ?, 1284][192, ?, 1412][193, ?, 1313][194, ?, 1273]
[195, ?, 1424][196, ?, 1284][197, ?, 1364][198, ?, 1239][199, ?, 1478]
[200, ?, 1429][201, ?, 1299][202, ?, 1339][203, ?, 1438][204, ?, 1385]
[205, ?, 1297][206, ?, 1346][207, ?, 1422][208, ?, 1340][209, ?, 1320]
[210, ?, 1299][211, ?, 1397][212, ?, 1349][213, ?, 1435][214, ?, 1243]
[215, ?, 1485][216, ?, 1369][217, ?, 1395][218, ?, 1291][219, ?, 1717]
[220, ?, 1261][221, ?, 1430][222, ?, 1261][223, ?, 1450][224, ?, 1427]
[225, ?, 1307][226, ?, 1285][227, ?, 1458][228, ?, 1310][229, ?, 1330]
[230, ?, 1337][231, ?, 1395][232, ?, 1378][233, ?, 1279][234, ?, 1443]
[235, ?, 1357][236, ?, 1374][237, ?, 1461][238, ?, 1373][239, ?, 1381]
[240, ?, 1357][241, ?, 1309][242, ?, 1346][243, ?, 1401][244, ?, 1354]
[245, ?, 1381][246, ?, 1409][247, ?, 1395][248, ?, 1244][249, ?, 1309]
[250, ?, 1304][251, ?, 1375][252, ?, 1226][253, ?, 1314][254, ?, 1184]
[255, ?, 1193]
N. Bytes File nasmdoc.pdf=870724
--------------------------------
[toc] | [prev] | [next] | [standalone]
| From | "io_x" <a@b.c.invalid> |
|---|---|
| Date | 2011-06-14 19:46 +0200 |
| Message-ID | <4df79e09$0$45733$4fafbaef@reader2.news.tin.it> |
| In reply to | #6068 |
"io_x" <a@b.c.invalid> ha scritto nel messaggio
news:4df794e8$0$45734$4fafbaef@reader2.news.tin.it...
>>i think there're some other chars can't be printed. see the demo of
>>your code. Note the last "PuTTY" brought by running your code.
>>
>>$ make && ./a.out ./intro.wmv
>>
>>[cut]
>
>>N. Bytes File ./a.out=665107
>>$ PuTTY
>
> i hope it not changed something on your tty...
> what about this?
> -------------
> #include <stdio.h>
> #include <stdint.h>
> #include <limits.h>
> #include <ctype.h>
>
> // macro for types
> #define u64 uint64_t
> #define u32 uint32_t
> #define u16 uint16_t
> #define u8 uint8_t
>
> // macro for function
> #define P printf
>
> // macro for keyWords
> #define G goto
> #define R return
> #define W while
> #define F for
>
> int main(int c, char** a)
> {u32 nc[256], i, cont, r;
> FILE *pf;
>
> if(sizeof(u32)!=sizeof(int)||CHAR_BIT!=8)
> {P("Incompatible with your sys\n"); R 0;}
> // P("c=%d s=[%s]\n", c, (a[0]==0?"NULL": a[0]));
> if(c<=1) {P("Uso: \">program.exe nomeFile\" \n"); R 0;}
> pf=fopen(a[1], "rb");
> if(pf==0){P("ERRORE: Non riesco a aprire il file\n"); R 0;}
> F(i=0; i<256; ++i)
> nc[i]=0;
> W(1){i=fgetc(pf);
> if(i==(u32)-1||i>=256)
> break;
> ++nc[i];
> }
in the count of each char i forgot to see for nc[]s overflow
W(1){i=fgetc(pf);
if(i==(u32)-1||i>=256)
break;
++nc[i];
if(nc[i]==0) G err1;
}
> if((i!=(u32)-1&&i>=256)||ferror(pf))
{err1: fclose(pf);
> err: P("Some error in read the file\n"); R 0;}
> fclose(pf);
> F(i=0, cont=0; i<256; ++i)
> {r=cont;
> cont+=nc[i];
> if(cont<r) G err;
> }
[toc] | [prev] | [next] | [standalone]
| From | Joe Pfeiffer <pfeiffer@cs.nmsu.edu> |
|---|---|
| Date | 2011-06-14 16:08 -0600 |
| Message-ID | <1bhb7s6p82.fsf@snowball.wb.pfeifferfamily.net> |
| In reply to | #6068 |
"io_x" <a@b.c.invalid> writes: > // macro for types > #define u64 uint64_t > #define u32 uint32_t > #define u16 uint16_t > #define u8 uint8_t > > // macro for function > #define P printf > > // macro for keyWords > #define G goto > #define R return > #define W while > #define F for Please, no.
[toc] | [prev] | [next] | [standalone]
| From | Ian Collins <ian-news@hotmail.com> |
|---|---|
| Date | 2011-06-15 08:47 +1200 |
| Message-ID | <95pvmaFt6eU1@mid.individual.net> |
| In reply to | #6053 |
On 06/14/11 10:19 PM, io_x wrote: > > this is my try, i know there will be error etc etc > i'm not perfect... > > #include<stdio.h> > #include<stdint.h> > #include<limits.h> > > // macro for types > #define u64 uint64_t > #define u32 uint32_t > #define u16 uint16_t > #define u8 uint8_t > > // macro for function > #define P printf Readers can stop here! -- Ian Collins
[toc] | [prev] | [next] | [standalone]
| From | Hans Vlems <hvlems@freenet.de> |
|---|---|
| Date | 2011-06-13 23:51 -0700 |
| Message-ID | <4f8a7346-e108-4211-be1e-dfdebddea775@16g2000yqy.googlegroups.com> |
| In reply to | #5916 |
On 12 jun, 22:47, Uno <U...@example.invalid> wrote:
> On 06/12/2011 10:24 AM, Joe Pfeiffer wrote:
>
> > Uno<U...@example.invalid> writes:
> >> So, why the seg fault?
>
> > Let's just say this code is a prime example of why I took points of on
> > student programs that had magic numbers (like 7000000 for instance) in
> > the executable code.
>
> There were a lot of problems with this source that needing ironing out,
> and I needed to start to somehwhere. When I've got a program that
> compiles, I like to have the magic numbers #defined. I haven't really
> done much C on a 64-bit processor, so my ballparking seems to be wanting.
>
> $ cc -Wall -Wextra -g hist3.c -o hist
> $ ./hist
> UCHAR_MAX + 1 is 256
> a[0] is 217337
> a[1] is 123676
> a[2] is 137894
> a[3] is 100155
> ...
> a[252] is 97099
> a[253] is 75547
> a[254] is 113450
> a[255] is 128194
> Counter reached 19573713
> Counter2 reached 19573712
> $ cat hist3.c
> #include <stdio.h>
> #include <limits.h>
> #define SIZE 20000000
> #define SIZE2 (UCHAR_MAX+1)
>
> int main(void)
> {
> int c;
> long counter = 0;
> long counter2 = 0;
> long a[SIZE2];
> long i, j;
> FILE *fp;
> fp = fopen("shoulder.wmv", "rb+");
> printf("UCHAR_MAX + 1 is %d\n", SIZE2);
> for (i = 0; i < (SIZE2); ++i) {
> a[i] = 0;
> }
> for (j = 0; j < SIZE; ++j) {
> c = fgetc(fp);
> counter++;
> if (c != EOF) {
> a[c] = ++a[c];
> } else
> break;
> }
> for (i = 0; i < (SIZE2); ++i) {
> printf("a[%ld] is %ld\n", i, a[i]);
> counter2 = counter2 + a[i];
> }
> printf("Counter reached %ld\n", counter);
> printf("Counter2 reached %ld\n", counter2);
> fclose(fp);
> return 0;
>
> }
>
> // cc -Wall -Wextra -g hist3.c -o hist
> $
>
> I needed two different SIZES, one that would be larger than the byte
> count of the file to be read and another that was one greater than
> UCHAR_MAX. Seems to behave. Thanks all for comments.
> --
> Uno
Before trying to get a program compiled correctly you might need to
spend some time on design first.
Hans
[toc] | [prev] | [next] | [standalone]
| From | Michael Press <rubrum@pacbell.net> |
|---|---|
| Date | 2011-06-15 13:06 -0700 |
| Message-ID | <rubrum-B28B16.13065415062011@news.albasani.net> |
| In reply to | #5881 |
In article <95j3bgFj2qU1@mid.individual.net>, Uno <Uno@example.invalid> wrote: [...] Code as disorganized as what you present here will fail with high probability. You have posted in clc enough to have heard most of the advice on writing good code, and heard all the mistakes tyros make, some of which you made here. Perhaps at this time you are incapable of writing good beginner's code even with help. What do you say? Do you want to tackle this? -- Michael Press
[toc] | [prev] | [next] | [standalone]
| From | Uno <Uno@example.invalid> |
|---|---|
| Date | 2011-06-16 01:38 -0600 |
| Message-ID | <95tq70Fc5lU2@mid.individual.net> |
| In reply to | #6116 |
On 06/15/2011 02:06 PM, Michael Press wrote: > In article<95j3bgFj2qU1@mid.individual.net>, Uno<Uno@example.invalid> > wrote: > > [...] > > Code as disorganized as what you present here will fail > with high probability. You have posted in clc enough to > have heard most of the advice on writing good code, and > heard all the mistakes tyros make, some of which you > made here. > > Perhaps at this time you are incapable of writing good > beginner's code even with help. What do you say? Do you > want to tackle this? > Get bent. That's english for your english sucks. And plonk. -- Uno
[toc] | [prev] | [next] | [standalone]
| From | Michael Press <rubrum@pacbell.net> |
|---|---|
| Date | 2011-06-16 00:54 -0700 |
| Message-ID | <rubrum-3AF7CA.00544616062011@news.albasani.net> |
| In reply to | #6139 |
In article <95tq70Fc5lU2@mid.individual.net>, Uno <Uno@example.invalid> wrote: > On 06/15/2011 02:06 PM, Michael Press wrote: > > In article<95j3bgFj2qU1@mid.individual.net>, Uno<Uno@example.invalid> > > wrote: > > > > [...] > > > > Code as disorganized as what you present here will fail > > with high probability. You have posted in clc enough to > > have heard most of the advice on writing good code, and > > heard all the mistakes tyros make, some of which you > > made here. > > > > Perhaps at this time you are incapable of writing good > > beginner's code even with help. What do you say? Do you > > want to tackle this? > > > > Get bent. That's english for your english sucks. What does English have to do with this? > And plonk. That's not English. -- Michael Press
[toc] | [prev] | [next] | [standalone]
| From | James Waldby <not@valid.invalid> |
|---|---|
| Date | 2011-06-16 16:59 +0000 |
| Message-ID | <itdcpp$s60$1@dont-email.me> |
| In reply to | #6140 |
On Thu, 16 Jun 2011 00:54:47 -0700, Michael Press wrote: > In article <95tq70Fc5lU2@mid.individual.net>, Uno <Uno@example.invalid> > wrote: >> On 06/15/2011 02:06 PM, Michael Press wrote: >> > ... Uno<Uno@example.invalid> wrote: ... >> > Code as disorganized as what you present here will fail with high >> > probability. You have posted in clc enough to have heard most of the >> > advice on writing good code, and heard all the mistakes tyros make, >> > some of which you made here. >> > >> > Perhaps at this time you are incapable of writing good beginner's >> > code even with help. What do you say? Do you want to tackle this? >> > >> Get bent. That's english for your english sucks. > > What does English have to do with this? > >> And plonk. > > That's not English. It certainly is. For example, the Wikipedia entry for Plonk (wine) says "Plonk is an unspecific and derogatory term in British and Australian English for wine that is notably inexpensive or judged to be of poor quality." However, Uno, who is the plonker[*] in the above exchange, undoubtedly meant it in the Plonk (Usenet) sense, "adding a particular Usenet poster to one's kill file". [*] <http://en.wikipedia.org/wiki/Plonker> -- jiw
[toc] | [prev] | [next] | [standalone]
| From | "J. J. Farrell" <jjf@bcs.org.uk> |
|---|---|
| Date | 2011-06-16 18:32 +0100 |
| Message-ID | <itden0$8ek$1@dont-email.me> |
| In reply to | #6139 |
Uno wrote: > On 06/15/2011 02:06 PM, Michael Press wrote: >> In article<95j3bgFj2qU1@mid.individual.net>, Uno<Uno@example.invalid> >> wrote: >> >> [...] >> >> Code as disorganized as what you present here will fail >> with high probability. You have posted in clc enough to >> have heard most of the advice on writing good code, and >> heard all the mistakes tyros make, some of which you >> made here. >> >> Perhaps at this time you are incapable of writing good >> beginner's code even with help. What do you say? Do you >> want to tackle this? >> > > Get bent. That's english for your english sucks. Interesting; not that it's topical, but what's wrong with his English? It looks fine to me.
[toc] | [prev] | [standalone]
Page 3 of 3 — ← Prev page 1 2 [3]
Back to top | Article view | comp.lang.c
csiph-web