As I said before, I'd prefer to get rid of csoundMessage0.

Original Message:
-----------------
From: Robert McNulty Junior bmj2001@bellsouth.net
Date: Thu, 4 Dec 2003 01:29:43 -0600
To: csound-dev@eartha.mills.edu
Subject: [CSOUND-DEV:3626] Re: error messages in envext


Would it be OK to get rid of it?
It was in Csound4, which working now for Cygwin.
I really need to get back to Csound5.
I'm learning what works and what does not.
I hacked pvl_main.c and another file.
Bobby

-----Original Message-----
From: owner-csound-dev@eartha.mills.edu
[mailto:owner-csound-dev@eartha.mills.edu]On Behalf Of John ffitch
Sent: Thursday, December 04, 2003 1:19 AM
To: Csound Developers Discussion List
Subject: [CSOUND-DEV:3625] Re: error messages in envext


CsoundMesage0 was a quick hack when I was creating a FLTK interface for 
the OSX system.  It was intended to be printf, but capturably by the GUI.  
For csound5 it really should not exist
==John ff



--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .

"gogins@pipeline.com"  writes:

> As I said before, I'd prefer to get rid of csoundMessage0.

For the build on utilities, csoundMessage0 is only referenced in cs.h
when FLTK_GUI is defined, i.e., when FTLK is installed.  The utilities
don't link with csound.c, so that is why it is undefined.  Here is the
relevant text in cs.h.

#if defined FLTK_GUI || defined WX_GUI
#define printf csoundMessage0
extern void csoundMessage0(const char *, ...);
extern void err_printf(char *, ...);
#else

$ grep csoundMessage0 *.cpp *.c *.h
fltk_gui.cpp:extern "C" void csoundMessage0(const char *, ...);
fltk_gui.cpp:void csoundMessage0(const char *format, ...)
ccsound.c:csoundMessage0(const char *format, ...)
cs.h:#define printf csoundMessage0
cs.h:extern void csoundMessage0(const char *, ...);
$ 

I wouldn't miss it.

John

what about getting rid of all dripple_printf stuff?

-m




On Thu, 4 Dec 2003, gogins@pipeline.com wrote:

> As I said before, I'd prefer to get rid of csoundMessage0.
>
> Original Message:
> -----------------
> From: Robert McNulty Junior bmj2001@bellsouth.net
> Date: Thu, 4 Dec 2003 01:29:43 -0600
> To: csound-dev@eartha.mills.edu
> Subject: [CSOUND-DEV:3626] Re: error messages in envext
>
>
> Would it be OK to get rid of it?
> It was in Csound4, which working now for Cygwin.
> I really need to get back to Csound5.
> I'm learning what works and what does not.
> I hacked pvl_main.c and another file.
> Bobby
>
> -----Original Message-----
> From: owner-csound-dev@eartha.mills.edu
> [mailto:owner-csound-dev@eartha.mills.edu]On Behalf Of John ffitch
> Sent: Thursday, December 04, 2003 1:19 AM
> To: Csound Developers Discussion List
> Subject: [CSOUND-DEV:3625] Re: error messages in envext
>
>
> CsoundMesage0 was a quick hack when I was creating a FLTK interface for
> the OSX system.  It was intended to be printf, but capturably by the GUI.
> For csound5 it really should not exist
> ==John ff
>
>
>
> --------------------------------------------------------------------
> mail2web - Check your email from the web at
> http://mail2web.com/ .
>
>