World: r4wp

Remember that a c-string! is a pointer to a memory address. Much 
like a string! in REBOL is a reference to the storage of a series 
value that can be referenced by multiple string!s, each with their 
own index

If you want to convert the content of your text file to an integer, 
my C library binding provides to-integer, just like in REBOL

Petr, the Red/System READ functions and the higher Red abstractions 
on top of it are already here. As I said yesterday, Doc is free to 
use parts of it when he makes a more elaborate I/O framework in Red

You're not wasting any time on them, are you (except by talking about 
them)? I need them now, and so do others

Thanks for the advice and comments, everyone!  I'm feeling really 
good about Red/System and the greater Red ecosystem now that I have 
a project under my belt.  Kaj's been an immense help and I thank 
others also for their input!

No console input command yet for Red or Red/System
prin "Number of sweets:" number-of-sweets: input
number-of-kids: ask "How many kids?"

Is the support planned? Will work nice with the kids sharing candy 
storyline making their program better.

Yes, there is, in my I/O binding and interpreter builds. The basic 
console has very little

Kaj, you said that 'read-file in Red/System automatically defines 
a large enough memory space for the file.  How about 'read-file-binary? 
 That one has a 'size parameter.  How can one determine how big to 
make that 'size parameter before reading the file?

You don't make it any size. It works the same as read-file and the 
READ function in REBOL: it allocates the storage for you

In the case of read-string you get a c-string!, so you can get the 
size with LENGTH?. For read-file-binary that's not possible, so you 
pass a pointer to an integer! to be informed about the read size

Sorry, read-file

Thanks for that.  Another detail I wasn't understanding correctly.

Where is RED at these days in comparison to R3?

Glass half full, half empty :-)

What are you interested in?

I guess more or less what is the major usuability items that are 
still lacking in each.  Maybe you can answer that towards what RED 
still lacks as a major need.

Garbage collector, error trapping, objects, floating point, PARSE, 
other complex datatypes

Some major ones there.

Yep, that's the glass half empty

Thanks Kaj.

There a timeline on those?

More like an order than an ETA, but you'd have to ask Doc

ok

Good info - thanks.

Hi Paul, we have some Windows drivers issues for you to solve, up 
to the challenge? ;-)

Hehe.  Possibly but got a new job that is hitting me hard.

Working mostly in SAN/NAS Cloud technologies.

What is your most pressing windows driver issue?

Kaj will explain it to you. :-)

ok

Basically, we have a minifilter driver in Red/System that can be 
installed through an INF file, but when started (using `sc start`) 
we get either error 1058 or error 2 (File not found).

SC is the service control manager command line utility

Is the process created as a service?

The INF file installs the filter driver as a service, yes.

ok

What is the verbose for 1058?

Just thinking loud, does that mean that the filter driver has to 
respond to service commands?

Yes most likely.

1058: I don't know, that's Kaj's error.

ok

Hmm, I guess we should try then implementing a suitable callback 
to answer properly to SCM commands...

Yes, still not sure what SC seen as file not found though.  But a 
process monitor from systems internals might tell us that.

Run procmon.exe against it and see if it records a specific file 
not found.

Thanks for helping on this, Paul!

Sure no problem.

Filemon: yeah, thanks for the reminder, forgot about it.

Procmon is the newer version of Filemon.

It gives you much more including registry, network, and profiling 
counters in addition to file system calls.

Thanks, Paul

When working with Windows debugging, I typically like to run a process 
through procmon.exe and dependancy walker profiling before tossing 
into the windows debugger.