1. bits.e
Where can I find bits.e? TIA jiri
ps For goodness sake, people, include *all* non-standard includes in your
packages.
Some libraries have many incompatible incarnations, some are buried in obscure
projects and some even have different authors.
2. Re: bits.e
jiri babor wrote:
>
> Where can I find bits.e? TIA jiri
>
> ps For goodness sake, people, include *all* non-standard includes in your
> packages.
>
> Some libraries have many incompatible incarnations, some are buried in obscure
> projects
> and some even have different authors.
>
hi Jiri
you did not say what app missed it out?
i download items from the contributions page , building my own archive.
i read others code to learn.
i did a search and found it in file "bits.zip". and it its also in the
contribution page. search for 'bits' and scroll down to the one put in
january 11 '05.
still using your widgets.
rudy
3. Re: bits.e
rudy toews wrote:
>
> jiri babor wrote:
> >
> > Where can I find bits.e? TIA jiri
> >
> > ps For goodness sake, people, include *all* non-standard includes in your
> > packages.
> >
> > Some libraries have many incompatible incarnations, some are buried in
> > obscure projects
> > and some even have different authors.
> >
>
> hi Jiri
> you did not say what app missed it out?
> i download items from the contributions page , building my own archive.
> i read others code to learn.
> i did a search and found it in file "bits.zip". and it its also in the
> contribution page. search for 'bits' and scroll down to the one put in
> january 11 '05.
>
> still using your widgets.
>
> rudy
Thanks, rudy. I was scanning Hayden McKay's svga lib. jiri
4. Re: bits.e
jiri babor wrote:
>
> Where can I find bits.e? TIA jiri
>
> ps For goodness sake, people, include *all* non-standard includes in your
> packages.
>
> Some libraries have many incompatible incarnations, some are buried in obscure
> projects
> and some even have different authors.
>
Hi Jiri,
I can understand your gripe in this situation but it's also been discussed
where some of us still using dialup don't want another copy of a big, but
fairly commom, lib (like win32 libs) just to check out some code.
If I was looking for bits.e, I would type "bits" into the archive search
engine. (I'm not trying to be a jerk here, it's just my natural tendancy.)
-- Brian
5. Re: bits.e
Brian Broker wrote:
>
> Hi Jiri,
>
> I can understand your gripe in this situation but it's also been discussed
> where some of us still using dialup don't want another copy of a big, but
> fairly commom, lib (like win32 libs) just to check out some code.
>
> If I was looking for bits.e, I would type "bits" into the archive search
> engine. (I'm not trying to be a jerk here, it's just my natural tendancy.)
>
> -- Brian
>
Brian, I did search using 'bits.*' (with wildcard). No match found. My mistake.
jiri
6. Re: bits.e
jiri babor wrote:
>
> Brian Broker wrote:
> >
> > Hi Jiri,
> >
> > I can understand your gripe in this situation but it's also been discussed
> > where some of us still using dialup don't want another copy of a big, but
> > fairly commom, lib (like win32 libs) just to check out some code.
> >
> > If I was looking for bits.e, I would type "bits" into the archive search
> > engine. (I'm not trying to be a jerk here, it's just my natural tendancy.)
> >
> > -- Brian
> >
>
> Brian, I did search using 'bits.*' (with wildcard). No match found. My
> mistake. jiri
>
No, it's RDS's mistake...
7. Re: bits.e
jiri babor wrote:
>
> posted by: jiri babor <jbabor at paradise.net.nz>
>
> Where can I find bits.e? TIA jiri
>
It is in bits.zip by Mike Duffy.
Regards,
Igor Kachan
kinz at peterlink.ru
