[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gambas-user
Subject:    Re: [Gambas-user] Extern howto/tutorial
From:       Benoît_Minisini <gambas () users ! sourceforge ! net>
Date:       2010-08-30 17:06:52
Message-ID: 201008301906.52890.gambas () users ! sourceforge ! net
[Download RAW message or body]

> Benoît Minisini ha scritto:
> >> Benoît Minisini ha scritto:
> > No: there is no HTML at all in your mail.
> 
> Very strange. A friend of us picked the same document from the gambas
> list, and put it on the italian site of gambas (www.gambas-it.org).
> Anyway, I attach a tarred copy of the new document, which contains
> corrections.

Thanks. I have put in on gambasdoc.org.

> 
> My copy of the documentation is different. With all evidence, a
> correction about this topic was added after I downloaded the gambas
> sources from sourceforge. Anyway, the important thing is that now the
> documentation is correct.

Ha! I have forgotten you are using an offline copy of the documentation.

> 
> > Note that 'WRITE #p, 0, 1' does not write one byte, but only the integer
> > 0 on four bytes. You must do 'WRITE #p, chr$(0), 1'
> > 
> > WRITE #p, outq writes four bytes as outq is an integer, not one byte.
> > 
> > And so on... I think you must check all your use of the WRITE
> > instruction, which write a number of bytes that depends on the datatype
> > of its second argument.
> 
> I corrected the above errors, and attach the revised project.
> It worked anyway, because the extraneous bytes written after the
> intended ones, were afterwards rewritten with correct values. Perhaps
> the compiler could reject statements like "write #p, 0, 1", or perhaps
> gambas2 is going to museum in favor of gambas3.
> 
> In a previous email I said that by declaring a constant as a byte, and
> then writing it out with a "write #pointer...", 4 bytes were written
> instead of one. This is not totally true - I did'nt verified. What is
> true, instead, is that declaring a constant as byte, and then writing it
> out to a stream, 4 bytes are written. This was verified in an old
> temptative of the drum machine, where OSS was used instead of alsa, and
> a gambas stream (file) was used to write to the file /dev/sequencer2.
> 

That is a bug, but I thought I have fixed it. I must check again then...

Regards,

-- 
Benoît Minisini

------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
Gambas-user mailing list
Gambas-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gambas-user

[prev in list] [next in list] [prev in thread] [next in thread]