|
-
May 27th, 2000, 02:10 AM
#1
Thread Starter
Fanatic Member
We are currently working on building new function libraries and we're wondering what kind of functions/properties/types/constants/enums/etc... people would like to see. Please reply to this post or e-mail us at [email protected] &/or [email protected]. Thank you very much.
-
May 27th, 2000, 02:18 AM
#2
Frenzied Member
what do you mean by a reference library.
-
May 27th, 2000, 02:21 AM
#3
Thread Starter
Fanatic Member
A reference library is a library of functions and procedures that you can use. For Example:
VBA is a function library. It contains functions such as:
msgbox
inputbox
all the basic functions you have in VB
We are simply creating new libraries to make all of our coding lives easier.
-
May 27th, 2000, 04:32 AM
#4
How about functions to access the registry? I hate having to re-copy my code every single time I try to do it. Or a better type of InputBox? Maybe a function that draws a gradient as well.
[Edited by Megatron on 05-27-2000 at 05:33 PM]
-
May 27th, 2000, 05:27 AM
#5
transcendental analytic
meg, why don't you put it in a module and use it instead?
Use  
writing software in C++ is like driving rivets into steel beam with a toothpick.
writing haskell makes your life easier:
reverse (p (6*9)) where p x|x==0=""|True=chr (48+z): p y where (y,z)=divMod x 13
To throw away OOP for low level languages is myopia, to keep OOP is hyperopia. To throw away OOP for a high level language is insight.
-
May 27th, 2000, 05:56 AM
#6
That's the hard part. It's about 100 lines of code and I have to copy it into the module each time.
If you mean I should have a template? I could, but if I'm going to make some other functions with it, I might as well get as much as i can and compile it into a DLL.
-
May 27th, 2000, 08:21 AM
#7
transcendental analytic
What, don't you know the good thing with modules? Use the same module over and over again, same code in same file, that's how to use it. Also my registry code is compressed to about 30 lines
Use
writing software in C++ is like driving rivets into steel beam with a toothpick.
writing haskell makes your life easier:
reverse (p (6*9)) where p x|x==0=""|True=chr (48+z): p y where (y,z)=divMod x 13
To throw away OOP for low level languages is myopia, to keep OOP is hyperopia. To throw away OOP for a high level language is insight.
-
May 27th, 2000, 07:41 PM
#8
No, I mean that when I want to use it in another App, I have to copy it from my App, to another App.
I don't want to use the same module for every App. I like to keep things organized.
-
May 27th, 2000, 09:20 PM
#9
transcendental analytic
Well you use your way, i use mine, basically i have a maindir for my applications in subdirs and another maindir with common code, (bas, cls ocx and other stuff), and it's yet organized.
Use
writing software in C++ is like driving rivets into steel beam with a toothpick.
writing haskell makes your life easier:
reverse (p (6*9)) where p x|x==0=""|True=chr (48+z): p y where (y,z)=divMod x 13
To throw away OOP for low level languages is myopia, to keep OOP is hyperopia. To throw away OOP for a high level language is insight.
-
May 28th, 2000, 04:02 AM
#10
But say if you have many different functions in your App that you've made yourself. Say, 30 for example. Instead of stacking it in one big module, wouldn't it be easier just to put it in a refrence library?
-
May 28th, 2000, 10:09 PM
#11
transcendental analytic
Actually I have almost all methods separated in different modules, so when i need one of them i just add it to the project. I don't think that big reference library is that good idea, it would just make your compiled even bigger.
Use
writing software in C++ is like driving rivets into steel beam with a toothpick.
writing haskell makes your life easier:
reverse (p (6*9)) where p x|x==0=""|True=chr (48+z): p y where (y,z)=divMod x 13
To throw away OOP for low level languages is myopia, to keep OOP is hyperopia. To throw away OOP for a high level language is insight.
-
May 28th, 2000, 10:26 PM
#12
I like modules better....
I love modules.....
modules are better than dll's....
because they dont have to be registered.... and end users cant screw with them(delete.. etc.)
-
May 29th, 2000, 02:31 AM
#13
transcendental analytic
That's my point about not making any dll's just compile everything in your project and you definitely have all code for your own use, not having other borrowing you dll's or the other way round, you using other's probably crap dlls.
Use
writing software in C++ is like driving rivets into steel beam with a toothpick.
writing haskell makes your life easier:
reverse (p (6*9)) where p x|x==0=""|True=chr (48+z): p y where (y,z)=divMod x 13
To throw away OOP for low level languages is myopia, to keep OOP is hyperopia. To throw away OOP for a high level language is insight.
-
May 29th, 2000, 02:39 AM
#14
Well when you put it that way, I guess modules would be better.
-
May 29th, 2000, 03:18 AM
#15
transcendental analytic
Modules rocks, and that's what they do, because you wont ever need to do program anything twice. If you do like me, you will end app with you're own huge supply of code
Use
writing software in C++ is like driving rivets into steel beam with a toothpick.
writing haskell makes your life easier:
reverse (p (6*9)) where p x|x==0=""|True=chr (48+z): p y where (y,z)=divMod x 13
To throw away OOP for low level languages is myopia, to keep OOP is hyperopia. To throw away OOP for a high level language is insight.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|
Reply With Quote