Hi Eric:
I will definitely take a look at your script.
To give you an example of the scope of what I do online:
I have one project in "c" that is 19,000 lines of code.
I have another that is about 9,000 plus the Borland
Database Engine (am rewritting THAT project to eliminate
the BDE, am considering a Rebol dbase module as one
alternative, although I have other resources.)
Thanks Eric.
:>) tim
At 09:52 AM 2/13/00 +0900, you wrote:
>
>Hi Tim,
>
>I enjoyed reading your description of your personal history and
>your project. I don't know very much about web programming, but
>I'll help when I can.
>
>You wrote:
>
>>P.S. I've got some ideas for a rebol "librarian",
>>that could fetch reusable subroutines like the one
>>the Eric wrote, and insert them into a project file.
>>More about that later.
>
>I'm not sure how necessary a project file is for REBOL programming,
>at least at this stage. I never got to the point in C where I needed
>a project file, but my understanding is that project files are handy
>to speed up the process of compilation (so that you don't have to
>recompile files if their code hasn't changed), and to link in compiled
>libraries.
>
>I think with REBOL you don't have to do (can't do) anything more
>complicated than including files. A lot of us have written utilities
>for this. I have one on rebol.org called dore.r that is a big help.
>It indexes all the *.r files below the REBOL home directory. Then you
>can do my-script.r with just:
>
> dore my-script ; takes a word! argument
>
>and,
>
> dore/maybe my-script
>
>will do that script only if it hasn't been done. This is the statement
>I use as an equivalent to an include statement. Also,
>
> dore/list my-script
>
>will print out a list of functions and objects defined in that script.
>I could send you the latest version if you're interested.
>
>See you,
>Eric
>
>
