[futurebasic] Re: [FB] scripting/back engines/passing params

Message: < previous - next > : Reply : Subscribe : Cleanse
Home   : October 2000 : Group Archive : Group : All Groups

From: tedd@...
Date: Wed, 25 Oct 2000 20:25:10 -0400
>Yes. The idea of the front end/back end is interesting. Passing the data via
>handles or records would give it maximum flexibility. This can also exploit
>FB's multitude of handle-type variables. For example, the caller and
>recipient might both know that what they are getting is "element as handle
>to myrecordtype1", while the generic middleman routines only need to be told
>that the parameter they are passing to and fro is a generic handle or long


Now you're venturing into Object Orientated Programming, where when you
call a function, you don't care what variables you send it, because at the
other end, the function that is used to process your data is dependant
upon, or chosen by, the variables you sent it.

For example, let's say I want to sort a group of numbers in an array -- so
I place the number array into a function called "FN sort(array(0))". The
function that is used to sort the array is determined by the variable
contained in the call. Now, I could do the same thing with an array of
strings and use the identical same function, namely "FN sort(array$(0)).
Why? Because I have sent the function an array of strings. You see, the
actual function used to sort the array, on the back-side, is different than
the preceding example because I sent it an array of strings instead of

In other words, it goes like this. I want to sort anything -- I always use
FN sort(). At the other end of the call, there are many different sort
functions. However, the function that is used in my specific call is
determined by the variables that are contained within the () portion of the

This type of programming makes the back-end complicated because you have to
account for every type of sort one could think of. While on the front end,
it's an easy call.

Now, consider that there are numerous programmers that could write hundreds
of different sort routines, each with a different set of variables to sort.
If one could combine all those different sort routines into one back-end,
then a single front-end call would suffice for all sorts -- therein lies
the beauty of OOP and libraries -- as I understand it.


Thinking about buying Jewelry?
Try our site: http://earthstones.com