OpenEuphoria

Re: And another thing (VOID in win32lib)...

• Posted by Derek Parnell <ddparnell at bigpond.com> Oct 04, 2003
• 362 views

----- Original Message ----- 
From: "Andy Serpa" <ac at onehorseshy.com>
To: "EUforum" <EUforum at topica.com>
Subject: RE: And another thing (VOID in win32lib)...


> 
> 
> Derek Parnell wrote:
> > 
> > 
> > ----- Original Message ----- 
> > From: "Andy Serpa" <ac at onehorseshy.com>
> > To: "EUforum" <EUforum at topica.com>
> > Sent: Saturday, October 04, 2003 6:16 PM
> > Subject: And another thing (VOID in win32lib)...
> > 
> > 
> > > The global VOID in win32lib causes a conflict with Diamond.
> > 
> > Sorry.
> > 
> > >  As far as I 
> > > can tell, VOID is only used a dummy variable internally to win32lib, and 
> > > 
> > > could be declared locally in win32lib.ew and winfile.ew without breaking 
> > > 
> > > anything?
> > 
> > You are wrong. I use VOID in nearly all my application code. Sure wish I 
> > could get Euphoria to ignore function returns.
> >  
> Aha.  I saw that VOID was declared locally in a number of the demo's, 
> and didn't see it mentioned in the docs, although maybe it is.  But 
> since it is a dummy, it wouldn't break anything if made local to 
> win32lib.ew, right?  (It is never assigned a value in one file that is 
> used in another.)  So as long as I declared it locally where needed, I 
> could unglobalize it in win32lib.ew, declare it locally in winfile.ew, 
> and remove the conflict that way...

Knock yourself out, kid.