I'm playing around with SNOBOL4 (49.6KB freeware) and I'm getting a 'Extended Error 183' message. Will someone please give me an idea what the problem could...
Searching with Google for "Extended Error 183", reveals that it seems to occur when trying to create a directory (or perhaps a file) that already exists. To...
Apparently it is trying to CREATE (specifically) a file (or subdirectory?) and that file (or subdirectory) already exists. Are you using the CSNOBOL one, or...
Thanks Ken. I thought it was an error issued by SNOBOL, did not stop to think that it could be coming from DOS. Basically, it is my standard play program,...
FWIW-- There appears to be a problem with the EXECUTE statement in SNOBOL4 when running in a DOS box under XP. The same program runs correctly on my WIN98...
- ... - Win98 is runs a real version of DOS. WinXP -- in contrast -- runs an application (attempting to) simulate DOS. This is a 3rd-party program which MS...
Interesting? Could be many things. Does it only occur when you are logged onto it? Does the same program run on another XP box okay? Gordon wrote: I *have*...
I've not seen this on ANY other machines, anywhere. Obviously I'm logged on, I wouldn't have access otherwise... The same program runs fine on other XP boxes,...
Gordon, it sounds like your problem may be due to a specific mother board, or combination of a certain processor and motherboard. Rather than just a quirk...
... I don't think so, since spitbol apps have worked perfectly with this identical processor and motherboard for many years. This lockup behavior began fairly...
Well -- maybe not a bug. Maybe "Working as designed". Here is some sample code: define('f()L') :(f_end) f L = 10 F = *(G + L) :(return) f_end f = f() G = 5 ...
Fred: You declared L to be a local variable in the define. If you remove it from the function declare your program should work as expected. It has something to...
... Yes. The key to understanding this is to be aware that there is only *one* name space in the system. Calling a function pushes the values of "local"...
Logan Yes, L is a local variable. No, removing it should (does) result in the exact behaviour exhibited. The idea is that a local L is created in the function...
Yes, but when a variable is restored, any unevaluated exmpressions created since the "push" occurred could be examined, and the variables deliberatly...
From: Fred Weigel ... What is "GC'd"? Garbage collected? This communication is the property of Qwest and may contain confidential or privileged information....
There is only one variable named "L". When f() is called, the current value of "L" (the null string by default) is pushed onto a stack and "L" is overwritten...
Hello Fred, It does not appear broken to me. And does not appear too differant to many other languages.. Yes, one has to be careful with variable names. But...
As I understand it, the point is that the restoration of the non-local value of L upon return from the function is not a matter of garbage collection (as you...
From: Fred Weigel ... I thought about this a lot yesterday. And even after reading the responses from some of the experts, I am not convinced that evaluating ...
Here's another way of thinking about it. When eval evaluates an unevaluated expression, it evaluates the expression in the current environment and not the...
... Absolutely, and this seems to have been the point of confusion. There are NOT two different variables "L". There is ONE variable L. The value it had upon...
... It seems to me that what Fred wanted was something amounting to: define('f()L') :(f_end) f L = 10 F = *[(G + ] L *[)] :(return) f_end where I am using...
... In that case, using a quoted expression is exactly what he could do: define('f()L') :(f_end) f L = 10 F = *('G + ' L) :(return) f_end This will give...
... WOW! My first reaction was "JEEZ! Does THAT work??!!" But on thinking about it, I guess it's plausible that it actually COULD! At least, it xould if you...
Right. What it shows is first and foremost that I should have checked what I suggested, by running it. In that case I would have corrected my suggestion as...
... Thank you. This is very interesting. Although I realised that conceptually what was needed was quoting the part that was to be non-local, I failed to...