Re: [cc65] Linking [s]printf breaks cbm_open?

From: Jakob Haufe <sur5r1sur5r.net>
Date: 2007-08-26 22:18:45
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ullrich von Bassewitz <uz@musoftware.de> wrote on Sun, 26 Aug 2007
20:05:11 +0200 in 20070826180511.GB22090@trixie.musoftware.de:

> On Sun, Aug 26, 2007 at 04:44:51PM +0200, Jakob Haufe wrote:
> > As soon as [s]printf is linked to the program, cbm_open always
> > return oserror=2 (file open). This happens even if [s]printf gets
> > never executed.
> 
> You cannot use standard file i/o and cbm file i/o together without
> problems. Both need file handles, and there is no way to allocate
> these handles when using standard file i/o invisible to the user.

Understood.

> You can however use sprintf - if it does not work (as you're claiming
> above), please send me a short example program via private mail.

I tried again. sprintf alone indeed is no problem. I must have missed
something that made me believe that sprintf is a problem, too.

> Please consider using either just the standard file i/o functions
> (fopen/fread/fwrite/fclose) or use direct console functions for
> output to the screen.

Is it possible to access a printer using fopen etc.?

Regards,
Jakob
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFG0eAq1YAhDic+adYRAtvXAJsFlgcR1uknpAkPoLdPVk9fOQXnYgCgxaoq
+MToLicfcsZyyK1qCgzdTuQ=
=slxW
-----END PGP SIGNATURE-----
N‹§²æìr¸›yúèšØ^–+-±éÝ™¨¥¶‰šŽŠÝ¢j&ºÊ·«y×°¶¬¶¸§‚éì¹»®&ÞqιŠ{ayºʇí…éš
Received on Sun Aug 26 22:18:19 2007

This archive was generated by hypermail 2.1.8 : 2007-08-26 22:18:21 CEST