Re: New keywords: ifdef, elsifdef, end ifdef
CChris wrote:
>
> Mike777 wrote:
> >
> > Kat wrote:
> > >
> > > Shawn Pringle wrote:
> > >
> > > <snip>
> > >
> > > > That would have been useful when win32lib.ew put a string type in their
> > > > library.
> > >
> > > Wait,, there's a string type in win32lib??
> >
> > type w32string Implements an ASCII string.
> >
> > Mike
>
> Sorry to nitpick, but...
>
> I'll change this doc entry anyway. User defined types in Eu hardly implement
> stuff, they just recognise it. A w32string is a plain sequence the contents
> of which are printable or control single byte chars. It doesn't implement
> char[]
> or TCHAR[] as such.
>
> btw I may consider tagging some user ctypes as printable, so as to allow DBCS
> chars in w32strings. Will
> be in 70.4a if it's delayed enough 
I downloaded the latest win32lib off the user contribs page, and did a
wordsearch in it for w32string, and found it is a type. Nothing uses it, nothing
manipulates the w32string in memory. Nothing puts a sequence into memory, and
nothing moves the w32string into a sequence. Near as i can tell, it's a
type-restricted sequence, not a C-type string in memory.
Not nearly like Bernie's mixedlib.e, which i'll hereby nominate as "should be in
Eu". But with integer values bigger than 32bits, of course. 
Kat
|
Not Categorized, Please Help
|
|
