Knew it wouldnt last !!!
------=_NextPart_000_003C_01C0022D.4B34A8A0
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Just a comment on the below statements made by simulat=20
I believe that the use of Euphoria should require like all shareware a =
usage time limit (just my opinion).=20
RDS has a powerfull tool for programming that doesnt require us to be =
proficient at other languages such as C, C++, Assembler
to be able to get code up and running faster than conventional ways and =
one that requires NO degree to see results.
for this, we should be greatfull and support RDS and, any future =
improvements that may make our ventures in programming
SAFEr, SIMPLEr, SEXYr, FUN I think that's the motto (sorry if it's not =
Robert). We will all win in the end if you just register.
Registration does make programming in Euphoria easier..(my opinion)
Hi Paul
It's not so bad - the 300 line limit isn't such a killer. I used =
Euphoria for a year and a half without registering. Robert's scheme of =
providing a fully functional package with the debugger crippled for big =
programs is very generous, and I hope quite effective in generating =
sales. It sure worked with me - by the time the 300 line limit became a =
real pain I was hooked on the language and had no choice but to buy.=20
The thing to realize is that the 300 line limit is only on the debugger. =
You can get around it in a couple of legal ways.
a) Don't use the debugger - it's a wonderful convenience, but not =
absolutely necessary.
b) If you're using an unstamped library, maybe try making a copy with a =
new name that has had everything that you don't need discarded. For =
example, with the pcsound.e (which I have not examined) you may be only =
using a couple of functions out of dozens provided. Take those couple =
out of pcsound.e and put them into something like paul.e. Then the =
library won't eat up your 300 lines all by itself.
c) Make bigger programs by writing and testing smaller modules that fit =
in the 300 line limit and then combining them when they are correct into =
a bigger program. You still have a bit of a debugging problem at the end =
of the process, but you have access to the debugger for creation of all =
the modules.
Onwards and upwards
Bye
Martin=20
simulat at intergate.bc.ca
------=_NextPart_000_003C_01C0022D.4B34A8A0
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4134.600" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>
<DIV><FONT size=3D2>Just a comment on the below statements made by =
simulat=20
</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>I believe that the use of Euphoria should require =
like all=20
shareware a usage time limit (just my opinion). </FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>RDS has a powerfull tool for programming that doesnt =
require=20
us to be proficient at other languages such as C, C++, =
Assembler</FONT></DIV>
<DIV><FONT size=3D2>to be able to get code up and running faster than =
conventional=20
ways and one that requires NO degree to see results.</FONT></DIV>
<DIV><FONT size=3D2>for this, we should be greatfull and support =
RDS and, any=20
future improvements that may make our ventures in =
programming</FONT></DIV>
<DIV><FONT size=3D2>SAFEr, SIMPLEr, SEXYr, FUN I think that's the motto =
(sorry if=20
it's not Robert). We will all win in the end if you just =
register.</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>Registration does make programming in Euphoria =
easier..(my=20
opinion)</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>Hi Paul</FONT></DIV>
<DIV><FONT size=3D2>It's not so bad - the 300 line limit isn't such a =
killer. I=20
used Euphoria for a year and a half without registering. Robert's scheme =
of=20
providing a fully functional package with the debugger crippled for big =
programs=20
is very generous, and I hope quite effective in generating sales. It =
sure worked=20
with me - by the time the 300 line limit became a real pain I was hooked =
on the=20
language and had no choice but to buy. </FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>The thing to realize is that the 300 line limit is =
only on the=20
debugger. You can get around it in a couple of legal ways.</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>a) Don't use the debugger - it's a wonderful =
convenience, but=20
not absolutely necessary.</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>b) If you're using an unstamped library, maybe try =
making a=20
copy with a new name that has had everything that you don't need =
discarded. For=20
example, with the pcsound.e (which I have not examined) you may be only =
using a=20
couple of functions out of dozens provided. Take those couple out of =
pcsound.e=20
and put them into something like paul.e. Then the library won't eat up =
your 300=20
lines all by itself.</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>c) Make bigger programs by writing and testing =
smaller modules=20
that fit in the 300 line limit and then combining them when they are =
correct=20
into a bigger program. You still have a bit of a debugging problem at =
the end of=20
the process, but you have access to the debugger for creation of all the =
modules.</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>Onwards and upwards</FONT></DIV>
<DIV><FONT size=3D2>Bye<BR>Martin </FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=3D2><A=20
=20
/BODY></HTML>
------=_NextPart_000_003C_01C0022D.4B34A8A0--
|
Not Categorized, Please Help
|
|
