[RQ.NET Dev]RE: New GUI?

[Brian C. B. <Bri...@sh...>]

Hi Taj,
> Me neither. We could write the backends in another language (eg, C++,
> C#,  Pascal, or KoolB) and then call them in RQ.NET--although this would
> be hard and be a pain.
That's one solution. But I think that when RQ.NET can compile itself, then
the backends can be separated off into there own DLLs.

So perhaps we just create an object for each backend:

CSharpBackend
CppBackend
AsmBackend
PascalBackend

To bad RapidQ didn't have polymorphism or we could just have one 'father'
class that all other backends were derived from and then select the actual
backend at runtime.

Something else that may work is function pointers. Store all the functions
for a backend in an array, and then select the array on runtime.

We'll think of something.

Sincerely,
Brian C. Becker @ www.BrianCBecker.com

Shall we accept good from God, and not trouble?