The GNU LGPL doesn't seem very draconian... just the usual stuff about releasing source-code with it, etc, and probably not using it to scam little old ladies out of their poodle's inheritance money.Tuxman wrote:...but also including licensing restrictions which make redistribution gross, at best.
I always release code anyway, as people are about as likely to actually buy my nonsense as they are to buy your nonsense 
, so that type of licence is no skin off me.Worse than that, really - at the time I was using T-Pascal on the Commodore-64 (very few proper compilers were 6502/6510-compatible back then), and only in the "hopeful-stage" of getting a faux-IBM machine (lots of lawn-mowing that summer, and tin-collecting in the winter) - so... I had a lot of time to kill before I actually managed to get Borland C on a "real" PC, which is why I was stuck with the trusty K&R paperback for inspiration, and not much else to work with. It's astonishingly difficult to get your head around pointers just by trying to create an interpreter by using the described "expected" results found in a book and reverse-engineering the abstract logic behind it. It was a very long year.Tuxman wrote:...didn't Turbo Pascal have Borland's compiler built-in? So you had a compiler - for a language other than C though
Come to think of it though, it was probably rather good practice for how I do it now... do all the "real" programming only in my head as I work outdoors all day, and then transcribe it in the evenings into the IDE, hope it works, and do bugfixing on the weekends. (My head, unfortunately, does not have a built-in debugger, which strikes me as a real limitation in the human-design.) Anyway, that's how 14-year-olds used to have to do it before the internet made trolling a national past-time.
Update: After finally managing to get some GTK3+ examples compiled, I don't think this is such a good idea, as it feels way too hands-off for my tastes (event-handling doesn't feel natural), and distribution on Windows is a joke for smaller projects. Probably best to stick with the familiar granular control the WinAPI affords when on Windows, and just use any old thing on Linux for laughs, forgetting any ideas about perfect GUI parity between the two. Oh well, so much for that approach to grand unification.
What made me think of this in the first place was that I was impressed with the Linux release of Beyond Compare (they develop with Embarcadero/Delphi) and their GUI's are virtually identical between Windows and Linux (and probably Mac too, given their attention to detail) - probably the best I've seen for something that originally started out as a Windows-only project. Their licences are conveniently cross-platform too, which is why I tried it. Embarcadero have really gotten their act together in the last couple of years, since releasing their (ridiculously expensive) 64-bit toolchain. Such cross-overs usually start the other way around, and one of the versions always ends up looking like a "poor port" of the other, with bad DPI scaling, etc. This one stood out as an exception. I get the feeling whatever widgety-UI-thingy they're using has been highly tweaked in-house.
Anyway, it's an exception I'm certainly not going to be able to imitate any time soon, as I'm certainly not switching to Delphi just for twice the shiny. 
I mean after all, it's just something that Nikos said is handled by Edit verbs (ignoring the many examples where this would be a real plum of a feature for a portable-only x2), but, instead we can work with paths that have 2^16 characters, which, you know, we run into *ALL* the time.
