Menu
▾
▴
unishell-discuss — Discussion about all things Unishell.
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
(2) |
|---|
|
From: Diogo K. <di...@ma...> - 2002-12-04 00:02:29
|
About modularity, I think there should be at least three modules: o A module to interface with the user (read commands, interpret them, show messages); o A module to execute the commands; o A module to control both the interface and the execution (a main module). I don't think #define'd commands are a good idea, because defines can store a very limited amount of information about the commands. One solution I like to use in my programs is to define a constant array of structures. In this case, each item of the array would have information about one command (name, syntax, arguments). If you observe most *nix systems, you'll see that most of the shell commands are implemented as external programs, and I see no reason to modify that. It would be nice, though, if we were able to abstract and standardize the command line parameters these programs use, like some sort of "translator". It would work like this: an entry in the config file like: "find: grep --recursive $(text) $(files)" Would allow us to define the find command as "find <text> <files>" or "<files> . find <text>" without breaking everything. It would also allow users to customize unishell to his/her distribution or operating system. Scripting is important too, IMO. It doesn't need to be much powerful, just if/for each/while/variables would be enough for me. -- Diogo Kollross di...@ma... -- __________________________________________________________ Sign-up for your own FREE Personalized E-mail at Mail.com http://www.mail.com/?sr=signup One click access to the Top Search Engines http://www.exactsearchbar.com/mailcom |
|
From: Diogo K. <di...@ma...> - 2002-12-02 21:12:06
|
Sorry, my mail server was out. Anyway, as for my status, here it is: I'm at heavy load at my university and at my job, so I wouldn't be able to code much. My interest in Unishell is most in designing/testing than anything else. About the syntax, I think it will be very influenced by the surrounding environment. It would be easier to have SVO ordering or OO at all if we were using an OO system behind it, like Java or Smalltalk. About 100% of command line *nix programs are made using an input/output model and I don't know how well it would fit in a new syntax. I know I wasn't much clear, but I'm in a hurry now. I'll be happy to continue this discussion tomorrow. -- Diogo Kollross di...@ma... -- __________________________________________________________ Sign-up for your own FREE Personalized E-mail at Mail.com http://www.mail.com/?sr=signup One click access to the Top Search Engines http://www.exactsearchbar.com/mailcom |
|
From: Raphael S. <rap...@gm...> - 2002-11-29 16:55:40
|
Hi All! This eMail brings you the tale of the Unishell v0.0.7. I felt like doing a release because, measured at our present release rate, many things have happened. Find attached below changelog, as well as bug and todo lists. Cheers, Raphael ---< snip >--- ==[ v0.0.7 Changes: o Implemented find_native_command() o Began to implement find_external_command() o Began to implement exec_cmd_*() o Now also properly finding out our name on DOS-like systems Notes: o This most definately is no administrative release. I did hack. ---< snap >--- ---< snip >--- ==[ #001 | o | s | - ] Does not give error message in POSIX mode when requested command could not be executed. ==[ #002 | o | s | - ] Does not append commandline options to command requested to run! ---< snap >--- ---< snip >--- A Add searching the given path for whatever is to be executed A Intercept Ctrl-C B Maybe also catch other keys... B Create a separate file for each exec_cmd_*(). They could become huge. B Decide what license to place Unishell under B Put license into license.txt file B Fix compiler warnings in src/main.c:96,97 B Implement exec_cmd_*() C Enable Makefile to work on arbitrary platforms C Put description of Unishell into Readme file ---< snap >--- -- Raphael Schmid Martin-Luther-Strasse 26 72224 Ebhausen GERMANY rap...@gm... Home: +49 (0) 7458-455289 On Site: +49 (0) 7452-808114 Mobile: +49 (0) 173-8757046 NIETS IS ONMOGELIJK |
|
From: Steve <ste...@ya...> - 2002-11-29 15:58:23
|
I read the development articles about Unishell on osnews.com, and it looks very interesting. I wish i could help out with the project, but I don't know any programming languages. I am about to compile Unishell v0.0.6 on my box with Red Hat Linux 8.0
-Steve
---------------------------------
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now |
