Anthony : Alain, any chance of getting read/write
access instead of read-only access for password-
authenticated users? I logged in with the userid/
password you gave me and can't upload anything...
Alain : You must log in as an authenticated to get read and WRITE
access. Only guests are
At 7:41 PM -0700 on 7/2/99, Alain Farmer wrote:
Alain : You're absolutely right. We do have a central site for posting
our latest code. It is accessible via FTP, ...
Alain, any chance of getting read/write access instead of read-only acess
for password-authenticated users? I logged in with the
Yennie : Do we have a central site in use for
posting our latest code? I hate to keep asking
different people for stuff to be individually sent.
Alain : You're absolutely right. We do have a central site for posting
our latest code. It is accessible via FTP, and the resulting URL will
look
Heh heh, yes I see your point =). Assuming it doesn't become a headache, I
vote for variable length strings. Perhaps NULL-terminated, if that is to be
the native string type anyway? Or else a p-string with two length bytes? I
really can't imagine anyone wanting object names longer than 65536
How about the time the lexical analyzer wastes scanning a 65536 char
object name?
And how unreadable your code will be with lots of 65536 char variables?
And the time it would take to write a script if all your variable names
were 65536
chars long?
Andre,
whether you're using an unsigned long
Sounds good. I think buttons, cards, stacks etc. will mostly fit in a
struct, also I'm not sure how we'd fit the names in there (I'd like to have
packed strings so we don't waste 256 bytes for each of them), or whether it
supports variably-sized arrays?
I don't think XDR expicitly supports
We might be able to save most of the space and just use
Str63s instead of Str255s, I for one never have object names longer than 63
characters. Of course that's just me...
Brian,
I think that, recalling past problems with 32k limits in HyperCard, we
might be best off with allowing very long
At 6:01 AM +0200 on 6/22/99, M. Uli Kusterer wrote:
* Interpreter: Now that we have an interpreter running, should we be dishing
out the implementation of the various xTalk commands? Perhaps we could
establish an interface so that anyone could, for example, write a C function
which implements
Brian,
I think that, recalling past problems with 32k limits in HyperCard, we
might be best off with allowing very long names for buttons and fields...
Heh heh, yes I see your point =). Assuming it doesn't become a headache, I
vote for variable length strings. Perhaps NULL-terminated, if that
At 12:15 AM +0200 on 6/24/99, M. Uli Kusterer wrote:
I think that, recalling past problems with 32k limits in HyperCard, we
might be best off with allowing very long names for buttons and fields...
I agree. Interpreter, for example, has no real limit of variable length,
function name length,
I'll be looking forward to the next snapshot- I'll have to break out my
Hypercard Script Language Guide and find some commands to crank out (and
crank up hopefully).
Tell me what commands and functions you want to code so we don't double up.
At 7:41 PM -0400 on 6/23/99, [EMAIL PROTECTED] wrote:
Perhaps NULL-terminated, if that is to be
the native string type anyway?
Akk... grrr... NO We have enough problems with that. I prefer length longs.
Or else a p-string with two length bytes?
Four bytes.
I
really can't imagine anyone
I
really can't imagine anyone wanting object names longer than 65536 characters
=P...
Well, no reason to not allow it. We'd have to add code everywhere to make
sure the length is not exceeded. And trust me, it's a pain in the a**.
How about the time the lexical analyzer wastes scanning a
At 3:08 PM -0400 on 6/21/99, [EMAIL PROTECTED] wrote:
Hello all,
I just joined the list a couple days ago, and decided to emerge from the
woodwork. I have a few miscellaneous thoughts, I apologize as they may have
already been discussed on the list earlier on.
* File format: ...
Contact Uli :)
Tell us more. Uli is doing some block file format and there is also a XML
format
being worked on I think. We are still in limbo about file format and new ideas
are very welcome.
Hi,
who's doing the XML? You know I was against it for various reasons, but if
there's something we should see we
* File format: I've heard through the grapevine that Uli was working on this
part. I'm not sure exactly what approach is being taken, but I can offer some
help in the cross-platform part of things. I recently worked on a project
using XDR (eXternal Data Representation) which allows you to
16 matches
Mail list logo
