User talk:EdK

Holy crap! Is there any language you don't know of?

Er...That question doesn't make much sense, does it? Anyway...

He doesn't know Tcl it seems, but then I'm biased... –Donal Fellows 10:54, 6 April 2010 (UTC)

I used Tcl very briefly in 1994. I did not care for it. Maybe I did not get to know it well enough. ---EdK 11:33, 6 April 2010 (UTC)

Well, there's quite a few examples here. (In fact, as of now there are only three that don't have Tcl solutions, of which it is inappropriate in two cases; I've been busy over the past year.) –Donal Fellows 12:05, 6 April 2010 (UTC)

Welcome to Rosetta Code! I'm Mike, and I noticed you created an account.

Some quick things you should be aware of:

Template:Mylang	Helps you show what languages you're familiar with, and helps us become aware of skills with languages we haven't seen.
Category:Unimplemented tasks by language	A place to find tasks missing solutions in various languages.
Blogs, twitter, facebook...	We have them, and are interested in yours.
Special:Webchat	Logs you into #rosettacode on the Freenode IRC channel. Not usually the most active communications medium, but occasionally helpful. It's logged at http://irclog.perlgeek.de/rosettacode/today.
Rosetta Code:Village Pump	A general Q/A and discussion area.
Rosetta Code:Finances	For most of Rosetta Code's history, expenses have been paid out of my pocket. I can't afford that much longer, and so you can see the state of Rosetta Code's finances, and how you may help. If you enjoy or are excited about the site, please consider reading through it.

Sorry for the boilerplate; it can be a bit difficult giving an individual greeting to each person. If you post information about your technical interests and background, I'll probably read it. If you already have put that kind of information on your user page, I probably already have; I'm always interested in how people do and can benefit from Rosetta Code. --Michael Mol 04:58, 5 April 2010 (UTC)

6800

Is 6800 assembly distinct from 6802? --Michael Mol 15:39, 21 May 2010 (UTC)

It has been several decades, but I remember needing to relearn some stuff when I moved from 6800 to 6502. Of course not as much as I had to relearn when moving from 6502 to 8080.

After some research I see the confusion. Quoting from Wikipedia:

At MOS, they quickly designed the 6501, a completely new processor that was pin-compatible with the 6800. This allowed it to be plugged into motherboards designed for the Motorola processor, although its instruction set was different. Motorola sued immediately, and MOS agreed to stop producing the 6501 and went back to the drawing board. The result was the "lawsuit-compatible" 6502, which was by design unusable in a 6800 motherboard but otherwise identical to the 6501. Motorola had no objection. MOS Technology 6502

So my memory is correct the instructions sets are different.User:EdK

Language and library organization

I really appreciate all the work you're doing with language, implementation and library association and documentation. I've got some ideas about associating those pages within the context of Semantic MediaWiki. Would you be interested in hashing this out and helping get it implemented? (It should only involve making changes to wiki pages, much like what you're already doing.)

My thoughts are:

• Distinguish between library, API and bindings between libraries and bindings to a language. That way:
  • An example said to use, e.g. PyGTK could be programattically assumed to use GTK, and an example said to use Xcb could be assumed to use X11.
  • An example using GLib could be assumed to be using OpenGL
  • GLUT is both an API and a library, but the original has long lapsed. There are replacements, though, and they could all be assumed to be implementations of GLUT.
  • The ISO89 C Runtime has an API spec, and any library/C language binding that correctly implements it could be reasoned by SMW to provide that runtime, and so any C example that uses an API spec could be reasoned to be an example use of those libraries.

That's the gist of the idea, for now. Does this strike your interest? --Michael Mol 17:28, 13 August 2010 (UTC)

I think I understand.

For example:

• pyGame is a binding of SDL to Python. SDL in turn uses OpenGL. This information should be captured somehow.
• There are several differant impementations of MPI, some of them have several language bindings. This should be captured.

but I am not sure why it matters what implementation of ISO89 is being used. They are generaly closly tied to the compiler, so specifing the compiler would generaly specify the library. Or am I misssing something?

I'm not exactly sure how to do this in this contect. -EdK 20:40, 19 August 2010 (UTC)

• I think the pyGame->SDL->OpenGL can be captured. User:Ce and User:Coderjoe have been doing a lot of work in sussing out the specifics of how SMW operates.
• I agree about the MPI considerations. It's rather similar to the variations between BASIC, FORTH, SQL or LISP implementations, when you look at it in a particular way. Each is similar, but significantly vary between implementations to the point where some implementations are considered to be their own languages. I'd love to find a way to decently capture that!
• I don't know that the particular version of the ISO89 runtime has practical value, but it is a distinction in how code may operate between compilers that purport to implement it, due to compiler-specific bugs and omissions. (If it were possible to break down the standard/implementation relationship by implemented/unimplemented/buggy components, I'd certainly prefer that!) --Michael Mol 15:55, 20 August 2010 (UTC)