[futurebasic] RE: [FB] Alternate method for fill by reference

Message: < previous - next > : Reply : Subscribe : Cleanse
Home   : May 2013 : Group Archive : Group : All Groups

From: "Edwards, Waverly" <Waverly.Edwards@...>
Date: Wed, 1 May 2013 11:22:25 -0500
That wasn't the direction I was headed in but those functions are very interesting.
I can use them in my project.   I have a few more days before classes start again so I thought I would jump on one of my pet projects.
I reminds of something I saw this morning in my converted code and realized that instead of seeing 

fileType = 12345689; // a long integer that represent an OSType

I saw this

fileType = 'WAVE';

and I was very happy.  I don't know when the FBtoC team made that change but it was very much welcome.



-----Original Message-----
From: futurebasic@... [mailto:futurebasic@...] On Behalf Of Bernie
Sent: Wednesday, May 01, 2013 12:03 PM
To: futurebasic@...
Subject: Re: [FB] Alternate method for fill by reference

Brian wrote:

> Wave wrote:
>> I seem to recall there is a possible issue using the ".nil&" syntax, having to do with byte order.
>> Maybe I'm wrong about that.
> Apple encourages use of Core Foundation as a replacement when possible because CF handles all endian issues automatically.


I haven't a clue where FillByReference is leading, but a couple of CF functions that may (or may not) be of interest:

include "ConsoleWindow"
include "Tlbx UTType.incl"

dim as CFStringRef string
dim as OSType type

string = fn UTCreateStringForOSType( _"WAVE" )
type = fn UTGetOSTypeFromString( string )
print type,
fn ConsolePrintCFString( string )
CFRelease( string )

To unsubscribe, send ANY message to: futurebasic-unsubscribe@...
To access the list archives, go to:  http://freegroups.net/groups/futurebasic/