Re: Static Libraries and Assembly Language


Betov wrote:

Still trying to escape the fact that you wrote what you wrote

What's to escape? The stuff works pretty good. And the people tend to
agree, given the number of peopl using it?

and prefer to switch to an easier topic?

What's hard about this one? You're just trying to switch the
conversation away from your ignorance of how libraries work.




Trying to hide the fact that you don't really have a clue what benefits
there are to static libraries?

No clown. I am showing the reason why using Static Libraries is an
absurd method, achieving, both at a time, to Black-Box Programming
and to bloated Binaries, for no reason.

Yes, we understand why you think it is bloat -- you think that linking
a module from a library links in the entire library. But you are wrong.
As is your argument that libraries and static linking are bloat. Given
that *you* seem to be the only one around here who thinks that
statically-linked libraries are an absurd programming method, and that
you're not convincing anyone that they are, I suspect that you should
probably reconsider your beliefs on this matter.


I am also showing that talking about "Code Re-Use", without saying
"re-use... _WHAT_", does not make any sense.

You are showing nothing. You wave your hands a lot. You scream and yell
a lot. You post a lot of smileys. But you don't *show* anything.



Then, i am also showing that, if the other guys prefer obsolete and
absurd methods, i do not care: Good for them.

You seem to be the only person prefering the "new" way. Why is that?



That's okay, your responses to others
here have amply demonstrated your ignorance with respect to that issue.

What could we have expected else, from a nobody who never did
anything real, but selling himself on the passing band-wagons?

No offense, but using library code to do "programming in the large" is
hardly a "passing band-wagon." That's been the conerstone of software
engineering for over 40 years. You seem to have fallen off the wagon
and don't even realize it.



Master Pdf:

"Hey! Look! M'a! I am an expert of Linkers Command Lines!"

Usual name calling rather than providing a technical defense of your
development mechanism. I guess this is what you mean by "showing".
Cheers,
Randy Hyde

.

Relevant Pages

  • Re: Problem with redefinition of stuctures
    ... Showing the lines of code that got the errors would be a major contribution to having ... functionality of their static libraries. ... CoreInclude\wce_time.h: see declaration of 'ftime' ...
    (microsoft.public.vc.mfc)
  • Re: is there anyone out there?
    ... I know that Millennium allows for specific ... showing only the books at that one location, ... We keep telling them that the other libraries' materials are ...
    (rec.arts.mystery)
  • Re: Wanted: Magic Lisp snippets
    ... Florian Weimer wrote: ... > Using libraries is cheating and doesn't count, ... Showing how to ... Lisp, _no_ libraries involved. ...
    (comp.lang.lisp)
  • [ANN] depdot 0.1.0 released
    ... As C and C++ projects get very large the libraries get to be ... very inter-dependent. ... have a means of showing what these dependencies are. ... The implementation language is C++. ...
    (comp.lang.cpp)
  • [ANN] depdot 0.1.0 released
    ... As C and C++ projects get very large the libraries get to be ... very inter-dependent. ... have a means of showing what these dependencies are. ... The implementation language is C++. ...
    (comp.lang.c)