santosh wrote:
> =ACa\/b wrote:
> > On Mon, 03 Jul 2006 09:23:55 +0200, "=ACa\\/b" <al@[EMAIL PROTECTED]
> wrote:
> > >.c2: [i+@[EMAIL PROTECTED]
r=3D@[EMAIL PROTECTED]
c=3Ds; ReadFile(r, a, j, c, 0);
> > ^^^^^
> > this should be r=3D[i+@[EMAIL PROTECTED]
> >
> > i wrote a function for to write in the files
> > if in b there is the int_file_descrittor, and any function return its
> > value in "a" in your opinione something of this kind can work in a
> > windows OS?
> >
> > int __stdcall write_m(int fd, char* base, int len)
> > {int a, b, k, mm, *s=3D&mm, b=3Dfd;
> > a=3DGetFileType(b); if(a=3D=3DFILE_TYPE_DISK) {k=3D-1; goto .c2;}
> > a=3DSetFilePointer(b, 0, 0, FILE_END);
> > if(a=3D=3D-1) {CF=3D1; a=3D0; goto .cf;}
> > k=3Da; a+=3Dlen; a=3DLockFile(b, k, 0, a, 0);
> > if(a=3D=3D0) {CF=3D1; goto .cf;}
> > .c2: c=3Dbase; r=3Dlen; a=3Ds; a=3DWriteFile(b, c, r, a, 0);
> > if(k=3D=3D-1) goto .c3;
> > a=3Dk; a+=3Dlen; a=3DUnlockFile(b, k, 0, a, 0);
> > if(a=3D=3D0) {CF=3D1; a=3D*s; goto .cf;}
> > .c3: a=3D*s; if(a!=3Dlen) {CF=3D1; goto .cf;}
> > CF=3D0;
> > .cf: return a;
> > }
>
> How are we expected to understand your private language. It's bad
> enough that there are several x86 assemblers with incompatible
> syntaxes, even with regards to basic instructions, without having to
> know the "hobby" languages of every Tom, Dick & Harry.
That's not a private language, it's very poorly written C that uses
non-****table compiler features. As for the "private language" in the
first post, it was followed up with the same thing in NASM syntax.
> For C code, comp.lang.c would be a better place and for assembler code,
> try to post in one of the well established syntaxes like MASM, NASM,
> FASM, GAS etc.
|
