From: Paul Lalonde <plalonde@telus.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] request for more GSoC project suggestions
Date: Wed, 25 Mar 2009 13:39:46 -0700 [thread overview]
Message-ID: <412F3DBF-E347-4D81-ACBA-9BFD8B383BE9@telus.net> (raw)
In-Reply-To: <9ab217670903251312t74e7b8fem89fd9f2807590972@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
A modern cfront is nearly impossible. Templates make it hella-hard.
And generics might actually be C++'s best feature, at least in
performance-code land.
Paul
On Mar 25, 2009, at 1:12 PM, Devon H. O'Dell wrote:
>
> 2009/3/25 Paul Lalonde <plalonde@telus.net>:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> I'd like to see a 3D graphics protocol. Then I could run the host
>> on some
>> linux or window or mac box to do the display, and run the graphics
>> app in
>> Plan9, or inferno, or ...
>>
>> And (heresy aside) I've love a way to compile C++ programs for
>> plan9. That
>> would give me a reason to get Plan9 up on this scary multi-core
>> part I'm
>> working on. Without C++ support, I can't run the principle
>> application I
>> need :-(
>
> Gogo reimplementation of cfront.
>
>> Paul
>>
>> On Mar 25, 2009, at 8:16 AM, Charles Forsyth wrote:
>>
>>>
>>> There are GSoC project suggestions at http://gsoc.cat-v.org/ideas/
>>> but I think more are needed, and that it would be especially good
>>> to have a further set of useful but simpler and smaller projects.
>>>
>>> Projects need to be non-trivial for GSoC, but shouldn't
>>> be hard enough that many of us would shun them (or indeed, have
>>> shunned
>>> them).
>>> Based on my experience several years ago,
>>> I'd also look for projects that are modular, so that the set of
>>> deliverables can be extended
>>> or reduced depending how things go. That worked well for the
>>> projects I was involved with.
>>>
>>> The problem with ports of the system or device driver writing, in my
>>> experience,
>>> is that satisfying though they are, and as necessary
>>> as they might be, they are typically quite hard to
>>> supervise, and will usually be fairly difficult for relative
>>> novices.
>>> There is quite a bit to learn for most students just to
>>> get started and be productive in the programming environment,
>>> although 9vx does make that much easier.
>>> Application-level projects are typically easier to
>>> supervise because they don't need specialised equipment,
>>> and many more people on this list and elsewhere can help
>>> with plausible advice, and also help debug when students are stuck.
>>> (Advice will
>>> sometimes be contradictory, but that's not a bad lesson to learn,
>>> too.)
>>> It's quite hard to help when special hardware or kernel-level
>>> debugging is
>>> involved.
>>> Because quite a bit in Plan 9 (or Inferno/9vx/p9p etc) is done at
>>> user-level that is done at kernel-level in other systems, that
>>> shouldn't
>>> narrow the scope much. I wrote "application-level" not just
>>> "user-level"
>>> earlier because I thought it would be good to have some
>>> interesting applications of the system. Of course, I don't mean
>>> to preclude system-level things when students are especially keen
>>> on that (as indeed I was during my school and university years).
>>>
>>> I don't know where the best place to suggest or discuss them
>>> would be,
>>> but I thought this list would reach nearly everyone interested.
>>>
>>
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.3 (Darwin)
>>
>> iD8DBQFJyoybpJeHo/Fbu1wRAoi3AKCTQLsrxzBt7m94P3LsOR+o85KungCfT6Ms
>> o+vaJtOAjx1IxDqCtWskyQY=
>> =FvNd
>> -----END PGP SIGNATURE-----
>>
>>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (Darwin)
iD8DBQFJypaTpJeHo/Fbu1wRAvhqAKDVGdbVdtqRqT811TJ/cixYcadiPwCgy/E8
/SJh8wFz5YXgVSg570Xmlnw=
=pomL
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2009-03-25 20:39 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 15:16 Charles Forsyth
2009-03-25 15:06 ` Devon H. O'Dell
2009-03-26 5:19 ` lucio
2009-03-26 13:18 ` Devon H. O'Dell
2009-03-26 15:03 ` lucio
2009-03-26 15:17 ` lucio
2009-03-25 19:57 ` Paul Lalonde
2009-03-25 20:12 ` Devon H. O'Dell
2009-03-25 20:19 ` erik quanstrom
2009-03-25 20:28 ` Devon H. O'Dell
2009-03-25 20:38 ` Chris Brannon
2009-03-26 0:47 ` erik quanstrom
2009-03-26 1:10 ` Chris Brannon
2009-03-26 2:02 ` Roman Shaposhnik
2009-03-25 20:39 ` Paul Lalonde [this message]
2009-03-25 21:12 ` Charles Forsyth
2009-03-26 1:11 ` Roman V. Shaposhnik
2009-03-26 1:51 ` Paul Lalonde
2009-03-26 2:01 ` Roman Shaposhnik
2009-03-26 2:01 ` Devon H. O'Dell
2009-03-25 20:40 ` James Tomaschke
2009-03-25 22:48 ` Paul Lalonde
2009-03-25 23:20 ` Devon H. O'Dell
2009-03-25 23:26 ` erik quanstrom
2009-03-26 2:03 ` Devon H. O'Dell
2009-03-26 4:43 ` erik quanstrom
2009-03-26 2:05 ` Roman Shaposhnik
2009-03-26 14:21 ` Joel C. Salomon
2009-03-26 15:09 ` Juan M. Mendez
2009-03-26 15:18 ` Devon H. O'Dell
2009-03-26 16:23 ` [9fans] LLVM & Exceptions (Was re. request for more GSoC project suggestions) Joel C. Salomon
2009-03-26 0:09 ` [9fans] request for more GSoC project suggestions Federico G. Benavento
2009-03-26 1:54 ` Devon H. O'Dell
2009-03-26 10:41 ` Charles Forsyth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=412F3DBF-E347-4D81-ACBA-9BFD8B383BE9@telus.net \
--to=plalonde@telus.net \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).