Can we standardise on the task in hand rsn? Due to being very busy and swanning off for some winter sun ( in Northumberland? ) for 2 weeks beforehand, I need to get started now.
Cheers, Steve On Wed, May 18, 2005 11:05 am, Nick Rout said: > > On Wed, 18 May 2005 10:01:06 +1200 > Carl Cerecke wrote: > >> Christopher Sawtell wrote: >> > On Tue, 17 May 2005 13:31, Volker Kuhlmann wrote: >> > >> >>> July: Bourne Shell, etc. ( bash, csh, ksh, zsh ) >> >> >> >>I volunteer for this. Drop csh, it's been superseeded by tcsh a decade >> >>ago. I would only mention tcsh in passing anyway, though the >> interaction >> >>with bash is interesting. I started programming in tcsh because it >> >>was/is(?) the default on Solaris, but switched to bash eventually. >> >>The relative portability between tcsh and bash is interesting too, but >> >>wouldn't fit into 15 minutes. >> > >> > >> > OK then, I have heard the message, so lets compact this scripting >> jamboree >> > into one, or possibly two, evenings. >> > >> > 7:30 Volker Kuhlmann: Bourne Shell, etc. ( bash, csh, ksh, zsh, >> etc. ) >> > 8:00 John Carter: Ruby. >> > 8:30 Carl Cerecke: Python. >> > >> > 9:00 SUPPER >> > >> > 9:30 Steve Holdoway: PHP. >> > 10:00 Zane Gilmore: Perl. >> > >> > 10:30 Everybody: FlameFest :-) >> > >> > 11:00 Vacate the premises. >> > >> > Personally I recon it's not possible to do justice to the subjects in >> the >> > times allowed, and would like to suggest that we spread this over 2 >> evenings. >> > I.E. put two of them ( e.g. perl and PHP ) off until August, but in an >> open & >> > democratic organisation who am I to say? >> >> I don't want it to go too late. (i.e. past 10pm). I still think >> 15minutes +5 min questions is plenty of time to give a good overview of >> a language. And that's about all I have time to prepare for anyway. >> Short, sharp, and to the point. > > Correct, It is not even meant to be anything approaching a complete > introduction to a language. It shows a few key points by a standardised > example (thereby giving a point of comparison) > > Perhaps we should have the FIRST talk of the evening being a intro to > scripts - what they are, what a #! line is for, the concept of stdin and > stdout and pipes. That should be enough to understand the rest and > should take no more than the standard 15 minutes allowed for the others. > > I say this because I helped a newbie yesterday who said "what is a > script? I have seen a lot on the mailing list, but I don't even know > what it is" > > Also I see no reason to exand on any of the differences between shell > implementations, again it is only an intro and should use bash as it is > the defined standard for linux (stop arguing). > > each presenter should also have his (verbosely commented) sample program > submitted to the organiser two days in advance so they can all be > printed out on as few sheets of paper as possible. terminals are damned > hard to see on the screen. > > The scripts should also be submitted in advance to the owner of the > laptop that will work the projector for testing on that system. We do > NOT want to be switching laptops all evening. > >> >> Organisations such as ours can suffer from indecision caused by >> leaderlessness. > > Quite right. As it was my idea, i am quite willing to make an executive > decision on the format. I will review the correspondence tonight and let > everyone know what I think. Then you are free to completely ignore me!! > >> >> Cheers, >> Carl. > > -- > Nick Rout > > -- Windows: Where do you want to go today? MacOS: Where do you want to be tomorrow? Linux: Are you coming or what?
