>Speaking of Sbasic... Wouldn't it be nice to avoid 'word clashes' by >following some kind of convention?
Interesting. I've been thinking about the same thing recently. And not just confined to clashing toolkits. By extending SBASIC in an uncontrolled manner you run the risk of older programs not being able to run properly because the names of procedures and functions they define happen to use clashing names. Ironically, the design concept of SBASIC to allow this extensibility could well become its biggest weakness for distributable 3rd party software utilities. Not a problem when you only run your own code because you are in complete control. Apart from appointing a registrar to allocate name prefixes (but then, how would you police their use?) I can only think of radical solutions to the problem, which would involve fundamental changes to the concept of SMSQ/E and SBASIC. Ian >-----Original Message----- >From: François Van Emelen [mailto:francois.vanemelen@;chello.be] >Sent: 25 October 2002 12:55 >To: [EMAIL PROTECTED] >Subject: Re: [ql-users] a small but perfectly formed update to QDOS >INTERNALS website <SNIP> >Speaking of Sbasic... Wouldn't it be nice to avoid 'word clashes' by >following some kind of convention? >An example to illustrate this? >I've just discovered W. Lenerz' ARRAY_BIN. Nice extension, but >unuseable. Why? It contains 'sort' and 'search' and these words are >already present in other extensions that I use every day.( reset, >search,sort,count,lower$,upper$,... are used in at least 3 >toolkits/extensions ... and they aren't compatible). Visit our website at http://www.ubswarburg.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments.
