[sane-devel] [patch] fix SANE_Device

2004-11-18 Thread Oliver Rauch
Am Don, 2004-11-18 um 06.09 schrieb Frank Zago: Oliver Rauch wrote: Am Mit, 2004-11-17 um 20.58 schrieb fz...@austin.rr.com: Hello Frank. I am not a fan of this patch. I think it will work but I think it is a hack. It seems that only a few backends have problems with this. A few

[sane-devel] [patch] fix SANE_Device

2004-11-17 Thread Mattias Ellert
This is a cryptographically signed message in MIME format. --ms030900080306060805090608 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Frank Zago wrote: SO? Is anyone for or against this patch? This patch introduces SANE backend internal

[sane-devel] [patch] fix SANE_Device

2004-11-17 Thread Frank Zago
Mattias Ellert wrote: Frank Zago wrote: SO? Is anyone for or against this patch? This patch introduces SANE backend internal definitions in the public sane.h header. Backend internal definitions should be in the sanei_*.h headers. If you really want different definitions of the

[sane-devel] [patch] fix SANE_Device

2004-11-17 Thread Oliver Rauch
Am Mit, 2004-11-17 um 06.04 schrieb Frank Zago: Frank Zago wrote: =20 The SANE standard defines the comunication between frontend and back= end. It does not define any structs that shall be internally used by the frontend or backend. I think the clean appoach is that the backend

[sane-devel] [patch] fix SANE_Device

2004-11-17 Thread fz...@austin.rr.com
Hello Frank. I am not a fan of this patch. I think it will work but I think it is a hack. It seems that only a few backends have problems with this. A few backend are creating the name of the manufacturer from the scsi inquiry. A lot of backends are creating their mode list from the

[sane-devel] [patch] fix SANE_Device

2004-11-17 Thread Oliver Rauch
--=-RUwrefXyfKzMY5rN2jAg Content-Type: text/plain Content-Transfer-Encoding: 7bit Am Mit, 2004-11-17 um 20.58 schrieb fz...@austin.rr.com: Hello Frank. I am not a fan of this patch. I think it will work but I think it is a hack. It seems that only a few backends have problems with

[sane-devel] [patch] fix SANE_Device

2004-11-16 Thread Frank Zago
Frank Zago wrote: =20 The SANE standard defines the comunication between frontend and backen= d. It does not define any structs that shall be internally used by the frontend or backend. I think the clean appoach is that the backend handles the texts intern= al as non const strings and only

[sane-devel] [patch] fix SANE_Device

2004-11-14 Thread Oliver Rauch
Am Sam, 2004-11-13 um 23.36 schrieb Frank Zago: Oliver Rauch wrote: Am Sam, 2004-11-13 um 21.26 schrieb Frank Zago: I guess the idea was that the strings shouldn't be changed after the SANE-Device pointer is returned to the frontend. Thsi behaviour should be made clear in the doc. To

[sane-devel] [patch] fix SANE_Device

2004-11-14 Thread Henning Meier-Geinitz
Hi, On Sun, Nov 14, 2004 at 12:14:10AM +0100, Oliver Rauch wrote: Please can you explain what error/warning the const produces on your system? e.g.: abaton.c: In function sane_abaton_exit': abaton.c:902: warning: cast discards qualifiers from pointer target type abaton.c:903: warning: cast

[sane-devel] [patch] fix SANE_Device

2004-11-14 Thread Oliver Rauch
Am Son, 2004-11-14 um 13.17 schrieb Henning Meier-Geinitz: Hi, =20 On Sun, Nov 14, 2004 at 12:14:10AM +0100, Oliver Rauch wrote: Please can you explain what error/warning the const produces on your system? =20 e.g.: abaton.c: In function sane_abaton_exit': abaton.c:902: warning: cast

[sane-devel] [patch] fix SANE_Device

2004-11-14 Thread Frank Zago
This is a multi-part message in MIME format. --020906070304060802060600 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ms-smtp-04.texas.rr.com id iAEJ34J5003498 =20 The SANE

[sane-devel] [patch] fix SANE_Device

2004-11-13 Thread Frank Zago
This is a multi-part message in MIME format. --020303030609050904070206 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit This patch removes the const from the name strings in SANE_Device. I didn't commit it because it might breaks stuff.

[sane-devel] [patch] fix SANE_Device

2004-11-13 Thread Henning Meier-Geinitz
Hi, On Sat, Nov 13, 2004 at 01:28:16PM -0600, Frank Zago wrote: This patch removes the const from the name strings in SANE_Device. I didn't commit it because it might breaks stuff. Be careful. SANE-Device is part of the SANE standard, so that would need to be changed also. However, I believe

[sane-devel] [patch] fix SANE_Device

2004-11-13 Thread Frank Zago
Henning Meier-Geinitz wrote: Hi, On Sat, Nov 13, 2004 at 01:28:16PM -0600, Frank Zago wrote: This patch removes the const from the name strings in SANE_Device. I didn't commit it because it might breaks stuff. Be careful. SANE-Device is part of the SANE standard, so that would need to

[sane-devel] [patch] fix SANE_Device

2004-11-13 Thread Oliver Rauch
Am Sam, 2004-11-13 um 21.26 schrieb Frank Zago: I guess the idea was that the strings shouldn't be changed after the SANE-Device pointer is returned to the frontend. Thsi behaviour should be made clear in the doc. To me, const means something else. Since this patch makes the variable

[sane-devel] [patch] fix SANE_Device

2004-11-13 Thread Frank Zago
Oliver Rauch wrote: Am Sam, 2004-11-13 um 21.26 schrieb Frank Zago: I guess the idea was that the strings shouldn't be changed after the SANE-Device pointer is returned to the frontend. Thsi behaviour should be made clear in the doc. To me, const means something else. Since this patch makes