Re: Rob?
Vincent wrote:
>
> Robert Craig wrote:
> >
> > I think you're getting a bit paranoid.
> > I'm not ignoring you. It's just that I sometimes
> > have to leave my computer to sleep, eat, or go out and buy food. 
> > I also have to serve many other customers. Customers who
> > disagree with you. Can all customers be right?
>
> I don't think it so much a matter of them disagreeing with me
> as it is with you disagreeing with them.
Hi Vincent,
I am sorry, but I am afraid that I'm strongly against your
solution on so called "include problem" for the official EU.
I have some not bad experience about including almost same libs
into EU programs. There is ru_eu_12.zip package in the Archive.
It is a bilingual English/Russian Euphoria. And it has bilingual
versions of all the official EU libs.
Sorry, but it is much more convenient way to have, say,
'misc.e' for the pure English standard lib and 'misc___r.e'
for almost same, but bilingual, lib rather than, say,
'misc.e' and 'russian/misc.e'.
Just try some real life concrete (specific) work about these
identical file names of libs and you'll too see lots of
confusions if these different libs have identical names.
Now I have NO problems and confusions, Euphoria cares,
and I'll never confuse my libs this way.
*The long file and path names were introduced to give us
a powerful tool for resolving any file name conflicts.*
Just use for your new lib some new good name and don't
worry be happy.
First time when this so called "include problem" poped up,
was Bensler's attempt to replace RDS standard libs with
his own unknown libs of identical names.
Nobody befor him tried that dubious trick against the
official RDS stuff.
[snip]
> > I'll grant you that you've answered 1 and 4, (though
> > the only person you referred to in 1 found a workaround,
> > and is "not demanding" a change to the language).
> > However I don't think you've provided a solution that
> > answers both 2 & 3.
>
> Ok... I've thought about dir() some more and concluded that you can use that
> instead?
>
> Let me explain...
>
> You could more or less do everything I mentioned with my second proposal, but
> instead of checking and storing for file sizes, check and store results of
> dir(f);
> where f means the current file name.
>
> So now in order for two or more files to be percieved as the same, the results
> of the current dir() and a stored dir() must be exactly the same.
>
> Example:
>
> {
> {
> {109,105,115,99,46,101}, -- file name
> {97}, -- attribute
> 7577, -- byte size
> 2006, -- year
> 1, -- month
> 11, -- day
> 15, -- hour
> 18, -- minute
> 4 -- second
> }
> }
>
> So in order for Euphoria to quitely ignore an include statement: Two or more
> different files
> will need to have the same exact names, attributes, and byte sizes. But it
> would also need
> to been modified the same exact year, month, day, hour, minute, and second!
>
>
> Heres another simplifed example showing this idea in action:
> }}}
<eucode>
> include file.e
>
> sequence a, b
>
> a = dir("C:\\EUPHORIA\\include\\misc.e")
> b = dir("C:\\EUPHORIA\\include\\machine.e")
>
> if equal(a, b) then
> puts(1, "The two files are most likely the same.\n")
> else
> puts(1, "Isn't that cute... but it's WROOONNNGGG!!\n")
> end if
>
> machine_proc(26, 0)
> </eucode>
{{{
>
> I think I like this one better than my 180 line solution.
> What do you think?
>
> This is just as simple as the file size solution but with an extremely higher
> degree of accuracy.
I'm sorry, but all these look like A-bomb against a sparrow.
Just renaming of a new file solves that 'problem'.
Path name and file name are different things, who cares about
file attributes? It is too large reading, if you want to learn
these attributes too.
Why you do not want to name some your new lib, say, as
"Vincent's_New_Lib_on_SVGA_graphics_for_DOS_and_Windows_and_Linux.e"?
Just name it so and I'll pay you my MicroDollars forever,
(if it will work on my machine)!
> Regards,
> Vincent
Good Luck!
Regards,
Igor Kachan
kinz at peterlink.ru
|
Not Categorized, Please Help
|
|
