There are a couple of extensions around which allow renaming of
proc/fn names. I think they do this by locating the token value in the
BASIC tables and either swapping the corresponding names around or
renaming them by patching. There's one in DIY Toolkit - can't remember
its name, something like
In a message dated 01/11/02 15:26:29 GMT Standard Time, [EMAIL PROTECTED] writes:
Rich - as you and your colleagues on the BASIC Reference Manual have
documented the various toolkits for that, have you got listings of the
keywords in the various toolkits listed by toolkit? That may help
Wolfgang
: Wednesday, October 30, 2002 10:05 PM
To: ql-users
Subject: Re: [ql-users] Sbasic extensions toolkits
Command: PREFER command toolkit
Example: PREFER cmp_string tkx
This email is intended only for the use of the addressees named above and
may be confidential or legally privileged. If you
Wolfgang writes,
WL©_ASEARCH - ? ;)
How about WL_IS_BEST_..
-groan- ;)
Besides, I think a name or
mnemonic should be helpful in reminding us what it does rather than
who did it. Dont you?
Sure I do - but then, MAT_xxx isn't really very clear either
It is if my toolkit happens
Wolfgang writes:
Toolkits will often be grouped for special purposes, such as array
manipulation, string parsing, or to manipulate some low-level object
(such as a database or timer, etc). Wouldnt it be more logical and
aesthetically pleasing to use prefixes such as MAT_, STR_, DB_,
On 30 Oct 2002, at 14:28, P Witte wrote:
WL©_ASEARCH - ? ;)
How about WL_IS_BEST_..
Youre right, but the chances of a clash are further reduced, and your
list would still help things along. Besides, I think a name or
mnemonic should be helpful in reminding us what it does rather
[EMAIL PROTECTED] wrote:
Sure I do - but then, MAT_xxx isn't really very clear either (IMHO).
If the list cleared all doubles anyway, we wouldn't even need
prefixes...
Usually every toolkit has a name. IMO the prefix should be derived
from that. This can as well be the name of the author
On Wed, 30 Oct 2002, Marcel Kilgus wrote:
Usually every toolkit has a name. IMO the prefix should be derived
from that. This can as well be the name of the author (anybody
remember Beule-Tools from Peter(?) Beule?).
As we're talking about SBASIC, I have spent much time thinking about this,
[mailto:dilwyn.jones;dj.softnet.co.uk]
Sent: Monday, October 28, 2002 7:36 PM
To: [EMAIL PROTECTED]
Subject: Re: [ql-users] Sbasic extensions toolkits
Hi Wolfgang, to get this started I'll send (privately) the list and
binary for DJToolkit which Norman Dunbar wrote to my spec. If needed
I'm sure I can get
On Tue, 29 Oct 2002 at 18:11:58, Dilwyn Jones wrote:
(ref: 004901c27f7a$21a515c0$a1075cc3blackpc)
you must have so much stuff on your web site, that you have
forgotton what
you have :o)
The source is available for download from your own web site.
Just my job driving me towards a nervous
Wolfgang writes:
I've read this thread about names clashes in toolkits etc.
with quite some interest.
3 - As a guideline, perhaps authors of future toolkits might
want to envisage that they should, indeed, preface their
extensions with, say, their initials, such as WL_ASEARCH
instead of ASEARCH
On 30 Oct 2002, at 1:10, P Witte wrote:
Toolkits will often be grouped for special purposes, such as array
manipulation, string parsing, or to manipulate some low-level object
(such as a database or timer, etc). Wouldnt it be more logical and
aesthetically pleasing to use prefixes such as
Hi all,
I've read this thread about names clashes in toolkits etc. with quite
some interest.
It would seem to me that, at least for the time being, the path of
least resistance would rather be to make sure that names just
don't clash, rather than try to devise various -very ingenious-
schemes
13 matches
Mail list logo
