Hi Jim,

> I already have, but it's a part of my commercial library I wanted to
> make a living on, and I hesitate to produce it. I did not want to go
> the donations route to make a living, with audits, audit trails, and
> the whole thing. If I give it to you, and you GPL it, then I have
> nothing to use in my commercial programs...

You as the author can easily dual-license your own code: One
copy as closed source for use in your own software and another
copy as GPL saying it can only be used in open source software.

Also, I do not understand what exactly the routine will do in
FreeDOS: If it will improve functionality of kernel or shell,
for example, then all closed source software can of course call
it without license problems. But your software will then need
FreeDOS or another DOS with similar functionality to work...

> it's about 130 lines of C++, so it's not real huge...

Then if I were you, I would just put the code in PUBLIC DOMAIN.
That way, both open source and closed source software would be
allowed your code for anything they want, without even having
to mention that it is from you. After all, it is only 130 lines
and not too valuable for you to give as a donation to the world.

>  there may be
> appropriate functionality provided in C++14 and Boost with the
> filesystem class, which handles filenames, paths, mungeing of same.

Boost is incredibly large, so it is very unlikely that anybody
would use it just to get one small function. There must be a
smaller library with a similar feature, for example some kind
of small-C-library maybe?

Regards, Eric



------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
_______________________________________________
Freedos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Reply via email to